3 ms·
Proper support for paged kernel memory? Async-by-default I/O? Must better power management (compare win vs linux battery life on same hardware).
by dmitrygr 6y ago
Proper support for paged kernel memory? Async-by-default I/O? Must better power management (compare win vs linux battery life on same hardware).
- pjc50 6y agoThe latter is definitely because the hardware manufacturers QA with it.
- marcodiego 6y agoBad power management is really manufacturers fault. See android phones or chromebooks that can last days without recharging.
- cheph 6y ago> Async-by-default I/O? What? Can you elaborate? I mean if you want non blocking IO from an fd in Linux, you can just do that. Not sure what defaults have to do with anything. Your code will still have to be written appropriately.
- dmitrygr 6y agoDefault in linux is read()/write() and be blocked. Doing async is a lot more work and until relatively (to NT timelines) recently quite limited (select). On NT the standard way is async, and doing things in the block-and-wait way is abnormal and unusual. Defaults matter. Because that's what most people will do.
- cheph 6y agoLinux use read(2)/write(2) for both blocking and non-blocking. Still don't understand what you mean by how NT does it. Either your code is written to accomodate Async IO or not.