lazy writer

NTFSD
1

hello,
is it possible by anyhow to hold and release lazy writer thread.

2

You want to block the lazy writer? Why? I suspect that there is something
else you are trying to do and have decided that a catch and release of the
lazy writer thread is the best solution. Perhaps you ought to explain what
your motivation for this solution to your problem is.

On Feb 3, 2008 1:30 AM, wrote:

> hello,
> is it possible by anyhow to hold and release lazy writer thread.
>
> —
> NTFSD is sponsored by OSR
>
> For our schedule debugging and file system seminars
> (including our new fs mini-filter seminar) visit:
> http://www.osr.com/seminars
>
> You are currently subscribed to ntfsd as: xxxxx@hollistech.com
> To unsubscribe send a blank email to xxxxx@lists.osr.com
>

–
Mark Roddy

3

Hi Mark,
actually i want to delay the flushing of files in controlled fashion. currently for files which are cached,lazy writer flushes them after specific time. thats why i want some mean to control lazy writer.Is there any way, for that other than controlling lazy writer thread.

4

> actually i want to delay the flushing of files in controlled
fashion.

…so the machine will run short of free/clean memory pages?

–
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
xxxxx@storagecraft.com
http://www.storagecraft.com

5

Maybe BSODs are more desirable than comitted files.

“Maxim S. Shatskih” wrote in message
news:xxxxx@ntfsd…
>> actually i want to delay the flushing of files in controlled
> fashion.
>
> …so the machine will run short of free/clean memory pages?
>
> –
> Maxim Shatskih, Windows DDK MVP
> StorageCraft Corporation
> xxxxx@storagecraft.com
> http://www.storagecraft.com
>
>

6

Maybe CcSetDirtyPageThreshold() might help, but I think that it is just hint for CM. AFAIK these threads which are 3 or 4 run at higher priority then usual and they are servicing lazy write, write behind and read ahead functionality. If you block one of them you risk deadlocks or system unresponsiveness.

-bg

7

Lazy writer is ExQueueWorkItem callback, don’t remember now whether it is
Critical or not such.

–
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
xxxxx@storagecraft.com
http://www.storagecraft.com

wrote in message news:xxxxx@ntfsd…
> Maybe CcSetDirtyPageThreshold() might help, but I think that it is just hint
for CM. AFAIK these threads which are 3 or 4 run at higher priority then usual
and they are servicing lazy write, write behind and read ahead functionality.
If you block one of them you risk deadlocks or system unresponsiveness.
>
> -bg
>

8

Hi!

Lazy writer is ExQueueWorkItem callback, don’t remember now whether it is
Critical or not such.

CM performs lazy writes and read-aheads using worker threads of “CriticalWorkQueue”.
Further it organizes the read-ahead & lazy write operations in 2 separate lists:

  1. Express queue
  2. Regular queue

Regards,
Ayush Gupta