How does the hex representation from hexdump or xxd work?
- ✅ How does the hex representations from
hexdumporxxdwork? What are the individual blocks, and why are the demarcated in that way? - What are the differences between
xxdandhexdump? - In what sense does the plaintext readout correspond to C headers?
Example hex dump output from xxd:
00000000: 5249 4646 0458 0600 5741 5645 666d 7420 RIFF.X..WAVEfmt
00000010: 1000 0000 0100 0100 c057 0100 80af 0200 .........W......
00000020: 0200 1000 6461 7461 e057 0600 0000 ffff ....data.W......
00000030: ffff 0000 0000 ffff ffff 0000 0000 ffff ................
What is the effect of the num_workers argument in data loading, and in general?
See os.sched_getaffinity(0) vs os.cpu_count()
How do you compute a (decimal) mod or modular division (//)?
- How are the numbers represented in binary
- How is modular division implemented naively?
- How is it actually implemented (efficiently)?
- How does Python handle this when the operands are of different types (float vs int)?
- How is modular division or mod implemented when working in other bases?
- Is the mod 2 operation particularly efficient on computers?
- Is the difference in efficiency noticeable? (Maybe leveraged for other bases)