3 ms·
NT sends CPU chasin' pointers between layers and layers of (filter) drivers in IRP madness. But yeah, it's so great on NT I can set that 16 kB of IRQL passive
by vardump 8y ago
NT sends CPU chasin' pointers between layers and layers of (filter) drivers in IRP madness.
But yeah, it's so great on NT I can set that 16 kB of IRQL passive level driver code pageable. Massive savings, and I'll only need to make sure I never ever run any of that code on IRQL dispatch or higher. If I mess up, the end user has a pretty blue screen to stare at.
I guess the impact of a pageable kernel was more important 10-20 years ago. Nowadays I rather allocate nonpageable memory just to avoid the headaches of not being able to actually use that memory at typical IRQLs a driver requires. For example DPCs run at dispatch IRQL, no access to pageable memory.