Linux.com

Does the pdflush mechanism still hold?

Link to this post 20 Jul 10

Does the pdflush mechanism still hold? The following functions and structs are disappeared when I browse the kernel 2.6.34 source code Does the pdflush mechanism still hold?

pdflush() __pdflush() pdflush_operation() wb_kupdate()

struct pdflush_work

Link to this post 23 Jul 10

Linux kernel : pdflush has been replaced by using flusing threads per backing device info (BDI)

Let me quote some important points :

The article Flushing out pdflush ( http://lwn.net/Articles/326552/) stated that pdflush has been replaced by flusing threads per backing device info (BDI).

quoted :" Jens Axboe in his patch set proposes a new idea of using flusher threads per backing device info (BDI), as a replacement for pdflush threads.

Unlike pdflush threads, per-BDI flusher threads focus on a single disk spindle. With per-BDI flushing, when the request_queue is congested, blocking happens on request allocation, avoiding request starvation and providing better fairness.

With pdflush, The dirty inode list is stored by the super block of the filesystem. Since the per-BDI flusher needs to be aware of the dirty pages to be written by its assigned device, this list is now stored by the BDI.

Calls to flush dirty inodes on the superblock result in flushing the inodes from the list of dirty inodes on the backing device for all devices listed for the filesystem.

As with pdflush, per-BDI writeback is controlled through the writeback_control data structure, which instructs the writeback code what to do, and how to perform the writeback. "

Who we are ?

The Linux Foundation is a non-profit consortium dedicated to the growth of Linux.

More About the foundation...

Frequent Questions

Join / Linux Training / Board