How to find out, what "pdflush" is working on
----- Original Message ----
Quoted 25 lines
From: Chris Snook <[email protected]>
To: Martin Knoblauch <[email protected]>
Cc: [email protected]; Peter zijlstra <[email protected]>; Fengguang Wu <[email protected]>
Sent: Tuesday, September 16, 2008 9:07:29 PM
Subject: Re: How to find out, what "pdflush" is working onQuoted 11 lines · Martin Knoblauch
Hi,
I find the following comment in
mm/pdflush.c/* * The pdflush threads are worker threads for writing back dirty data. * Ideally, we'd like one thread per active disk spindle. But the disk *
topology is very hard to divine at this level. Instead, we take * care in
various places to prevent more than one pdflush thread from * performing writeback against a single filesystem. pdflush threads * have thePF_FLUSHERflag set incurrent->flagsto aid in this. */Quoted 6 lines
Is there a way to find out what a certain instance of "pdflush" is working on? Like which block-device or which fliesystem it is writing to? I am still (2.6.27) trying to track down why writing a single file can make linux very sluggish and unresponsive. If that happens I usually see all possible 8 "pdflush" threads being in "D"-state. According to above comment only one of them should be really busy.
Quoted 3 lines
The key word is "ideally". We'd like it to work that way, but it doesn't. Patches to fix this are welcome.
Now, I am pretty much aware that apparently things are not "ideal". Therefore my question. Because before doing patches, one has to analyze.
Cheers
Martin