3 ms·
Does anyone know why hasn't NT become a tickless kernel? Is it some binary compatibility of the drivers thing?
by monocasa 6y ago
Does anyone know why hasn't NT become a tickless kernel? Is it some binary compatibility of the drivers thing?
- dmitrygr 6y agoConsidering that it is VASTLY better for battery runtime than Linux on same hardware, I guess ticklessness ain't all that important.
- monocasa 6y agoIt's just a cleaner design, having implemented a tickless kernel for an RTOS. All of these "what is the actual timer frequency" questions that get more and more complicated as you're doing more (and other contexts are doing more) just sort of disappear.
- brucedawson 6y agoWhat did you do for timer coalescing? If every thread can request a custom wakeup time then power consumption goes up. If wakeups are coalesced then what algorithm do you use to coalesce them, and how much movement in wakeup times do you allow? Depending on how you coalesce timers you can very easily find yourself reinventing the basics of what Windows does. The Windows system also gives you a very cheap to read timer counter which is a nice attribute. The Windows system is frustrating, especially for those who don't understand it, but it does have some excellent attributes.
- zlynx 6y agoThat is your default Linux configuration. The distros tend to err on the side of functional systems but higher power use. Start tweaking things like the stuff found in powertop. If your hardware is pretty standard Intel stuff you can get very low. For example, my Dell laptop will idle at 0.5 W with the display off, the SSD, USB, WiFi and PCIe bus all at idle. That's about 5 days of power on battery. About equal to what any version of Windows can do with Modern Standby settings.
- dmitrygr 6y ago5 years ago I would have done that. And I did. A number of times. it never even approaches the runtime of Windows. Nowadays, I don't waste my time. I pay Microsoft for windows license, and do all my work in a Linux VM. Believe it or don't, this produces longer battery lives.
- trevorishere 6y agoAs of Windows 8, it is tickless (along with XNU and Linux). Windows refers to this as "dynamic tick".
- monocasa 6y ago> What this means is that timeBeginPeriod still sets the global timer interrupt interval, on all versions of Window. We can tell from the results of timeGetTime() that the interrupt fires on at least one CPU core at that rate, and the time is updated. Maybe I'm misunderstanding that sentence, but it doesn't sound tickless. Digging into dynamictick, it sounds like they can suspend the timer interrupt for some ticks, but there's still a regular timer tick going off rather than setting up the timer for each next event like you'd see in a tickless design.
- brucedawson 6y agoFunctions like GetTickCount() need to read the tick count which is updated by the interrupt. Changing the behavior of GetTickCount() would be difficult and would likely be less efficient. So, NT can't become completely tickless - there needs to be an interrupt to increment that counter. Realistically there will almost always be some thread that wants to wake up then so the recurring interrupt probably doesn't cost anything.