Pierre Schweitzer c4f58bbfd8 [NTOKSRNL] Don't blindly schedule read-ahead on CcCopyRead() call. ... This avoids locking Cc for too long by trying to read-ahead data which is already in cache. We now will only schedule a read ahead if next read should bring us to a new VACB (perhaps not in cache). This notably fixes Inkscape setup which was slown down by read-ahead due to continous 1 byte reads. Thanks to Thomas for his help on this issue. CORE-14395		2018-02-28 20:58:36 +01:00
..
cacheman.c	[NTOS:CC] Avoid some magic numbers.	2018-02-22 14:03:03 +01:00
copy.c	[NTOKSRNL] Don't blindly schedule read-ahead on CcCopyRead() call.	2018-02-28 20:58:36 +01:00
fs.c	[NTOSKRNL] Fix a ****ing bug where private cache map was deleted in CcUninitializeCacheMap()	2018-02-08 14:15:02 +01:00
lazywrite.c	[NTOSKRNL] In debug builds, print more information about the top level IRP in the Cc worker thread	2018-02-10 23:50:26 +01:00
mdl.c
pin.c	[NTOSKRNL] Add the CcPinReadWait and CcPinReadNoWait counters	2018-02-24 14:52:04 +01:00
view.c	[NTOSKRNL] Avoid private cache map allocation for the first handle	2018-02-09 21:52:41 +01:00