Again for completeness, the engineering choice is between a system managed resource and a dedicated resource. If the management of the resource is critical, or even important, to functionality, then it is generally irresponsible to rely on undocumented behaviour. But if the resource is not vital, then why write, and test, your own code when Microsoft has done that work for you. The point is that it is an engineering choice and that the same kind of considerations apply for thread pools
And yes, the newly invented lookalike list should be considered identically equal to a lookaside list regardless of what my spellchecker might think.
Sent from Surface Pro
From: xxxxx@osr.com
Sent: Monday, April 14, 2014 10:52 PM
To: Windows System Software Devs Interest List
Sorry, can’t agree there.
Insufficient advantage to system managed look-asides for me to subject my driver to an arbitrary and undocumented allocation and deal location strategy.
There’s good citizenship, there’s selflessness, and then there’s just plain dumb. Using system managed look asides falls into the last category in my book.
I’m not saying “don’t trim on system memory pressure”. I AM saying don’t dont subject your driver to arbitrary trim rules written by somebody else with no thought or knowledge at all about how it will affect your driver. I call that just plain silly. Even on Phone.
Peter
OSR
@OSRDrivers
NTDEV is sponsored by OSR
Visit the list at: http://www.osronline.com/showlists.cfm?list=ntdev
OSR is HIRING!! See http://www.osr.com/careers
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer