On Mon, 2011-04-18 at 14:46 +0530, Raghavendra D Prabhu wrote:I checked the callgraph of bdi_wakeup_thread_delayed and found out thatI have set it to 500 centisecs as that is the default value of
dirty_writeback_interval. I used this logic for following reason: the
purpose for which dirty_writeback_interval is set to 0 is to disable
periodic writeback
(http://tomoyo.sourceforge.jp/cgi-bin/lxr/source/fs/fs-writeback.c#L818)
, whereas here (in bdi_wakeup_thread_delayed) it is being used for a
different purpose -- to delay the bdi wakeup in order to reduce context
switches for dirty inode writeback.
But why it wakes up the bdi thread? Exactly to make sure the periodic
write-back happen.
Attachment:
pgp00000.pgp
Description: PGP signature