Aug 11, 2007, 22:00 (0 Talkback[s])
WEBINAR: On-demand webcast
How to Boost Database Development Productivity on Linux, Docker, and Kubernetes with Microsoft SQL Server 2017 REGISTER >
"Ingo Molnar pushed a series of patches to his Completely Fair
Scheduler code upstream that were merged into the mainline kernel.
He explained the reason for so many small patches, 'the main reason
is the safe and gradual elimination of a widely used 64-bit
function argument: the 64-bit 'now' timestamp.' In addition to the
many small patches removing the 64-bit 'now' timestamp, he
"'These changes are necessary for 3 reasons: firstly they
address the 'there's too much 64-bit stuff in the scheduler'
observation. Secondly, it's not directly visible but these changes
also act as a correctness fix for an obscure (and minor) but
not-too-pretty-to-fix accounting bug: idle_balance() had its own
internal notion of 'now', separate from that of schedule().
Thirdly, this debloats sched.o quite significantly...'"