George Bișoc 578f2fc512 [NTOS:CM] Don't lazy flush the registry during unlocking operation ... Whenever ReactOS finishes its operations onto the registry and unlocks it, a lazy flush is invoked to do an eventual flushing of the registry to the backing storage of the system. Except that... lazy flushing never comes into place. This is because whenever CmpLazyFlush is called that sets up a timer which needs to expire in order to trigger the lazy flusher engine worker. However, registry locking/unlocking is a frequent occurrence, mainly when on desktop. Therefore as a matter of fact, CmpLazyFlush keeps removing and inserting the timer and the lazy flusher will never kick in that way. Ironically the lazy flusher actually does the flushing when on USETUP installation phase because during text-mode setup installation in ReactOS the frequency of registry operations is actually less so the timer has the opportunity to expire and fire up the flusher. In addition to that, we must queue a lazy flush when marking cells as dirty because such dirty data has to be flushed down to the media storage of the system. Of course, the real place where lazy flushing operation is done should be in a subset helper like HvMarkDirty that marks parts of a hive as dirty but since we do not have that, we'll be lazy flushing the registry during cells dirty marking instead for now. CORE-18303		2022-12-23 19:45:13 +01:00
..
cmake	[ASMPP] Implement asm preprocessor	2022-12-01 15:21:59 +02:00
include	[XDK] Silence some GCC x64 warnings	2022-12-01 15:21:59 +02:00
lib	[NTOS:CM] Don't lazy flush the registry during unlocking operation	2022-12-23 19:45:13 +01:00
tools	[ASMPP] Implement asm preprocessor	2022-12-01 15:21:59 +02:00