Pierre Schweitzer 7e550edb26 [NTOSKRNL] Drop the always running thread for lazy writer. ... Instead move to a threading model like the Windows one. We'll queue several work items to be executed in a system thread (Cc worker) when there are VACB that have been marked as dirty. Furthermore, some delay will be observed before action to avoid killing the system with IOs. This new threading model opens way for read ahead and write behind implementation. Also, moved the initialization of the lazy writer to CcInitializeCacheManager() it has nothing to do with views and shouldn't be initialized there. Also, moved the lazy writer implementation to its own file. Modified CcDeferWrite() and CcRosMarkDirtyVacb() to take into account the new threading model. Introduced new functions: - CcPostWorkQueue(): post an item to be handled by Cc worker and spawn a worker if required - CcScanDpc(): called after some time (not to have lazy writer always running) to queue a lazy scan - CcLazyWriteScan(): the lazy writer we used to have - CcScheduleLazyWriteScan(): function to call when you want to start a lazy writer run. It will make a DPC after some time and queue execution - CcWorkerThread(): the worker thread that will handle lazy write, read ahead, and so on		2018-02-07 21:37:17 +01:00
..
section	[NTOS] Fix 64 bit warnings	2018-01-14 13:54:14 +01:00
cachesub.c
copysup.c
fssup.c
lazyrite.c
logsup.c
mdlsup.c
newcc.h	[NTOSKRNL] Drop the always running thread for lazy writer.	2018-02-07 21:37:17 +01:00
pinsup.c