| |||||||||||||
PG_reserved, VM_RESERVED, and VM_UNPAGEDPG_reserved, VM_RESERVED, and VM_UNPAGEDPosted Nov 23, 2005 15:46 UTC (Wed) by Baylink (subscriber, #755)Parent article: PG_reserved, VM_RESERVED, and VM_UNPAGED
> But going into a bunch of drivers and tweaking their memory management code when this kernel is already at a -rc2 release looks like a certain way to introduce obscure bugs. So Hugh decided to go in and make fundamental changes to the low-level memory management code instead.
Cause, um, that's so much safer.
Right? :-)
(Log in to post comments)
PG_reserved, VM_RESERVED, and VM_UNPAGED Posted Nov 25, 2005 0:45 UTC (Fri) by amikins (guest, #451) [Link] Yes, because everyone knows that driver code is written by crazy and dangerous people, and poking the driver code the wrong way will cause them to gnash their teeth and attack anything adjacent to their own context.
The VM subsystem, on the other hand, is known to be well behaved and obedient.
(No, really. I'm totally serious. Absolutely. This is the truth. Honest.)
|
|||||||||||||