| To: | Török Edwin <edwintorok@xxxxxxxxx> |
|---|---|
| Subject: | Re: xfsaild causing 30+ wakeups/s on an idle system since 2.6.25-rcX |
| From: | Linda Walsh <xfs@xxxxxxxxx> |
| Date: | Mon, 18 Feb 2008 15:22:02 -0800 |
| Cc: | xfs@xxxxxxxxxxx, Linux Kernel <linux-kernel@xxxxxxxxxxxxxxx>, Arjan van de Ven <arjan@xxxxxxxxxxxxxxx> |
| In-reply-to: | <47B863A9.5070206@xxxxxxxxx> |
| References: | <47B863A9.5070206@xxxxxxxxx> |
| Sender: | xfs-bounce@xxxxxxxxxxx |
| User-agent: | Thunderbird 2.0.0.9 (Windows/20071031) |
Not to look excessively dumb, but what's xfsaild? xfs seems to be sprouting daemons at a more rapid pace these days...xfsbufd, xfssyncd, xfsdatad, xfslogd, xfs_mru_cache, and now xfsaild? Not a complaint if it ups performance, but I do sorta wonder what all of them are for and why they are needed "now" but not for, say, kernels before 2.6.18 (arbitrary number picked out of hat). Like bufd writes out buffers, logd writes/hands the log, datad? Isn't the data in buffers? mru_cache? -- isn't that handled by the linux block layer? Sorry...just a bit confused by the additions... Are there any design docs (scribbles?) saying what these do and why they were added so I can just go read 'em myself? I'm sure they were added for good reason...just am curious more than anything. Thanksd -lindad |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: tuning, many small files, small blocksize, Linda Walsh |
|---|---|
| Next by Date: | [patch] Don't change ctime in truncate is size does not change, David Chinner |
| Previous by Thread: | Re: xfsaild causing 30+ wakeups/s on an idle system since 2.6.25-rcX, David Chinner |
| Next by Thread: | Re: xfsaild causing 30+ wakeups/s on an idle system since 2.6.25-rcX, David Chinner |
| Indexes: | [Date] [Thread] [Top] [All Lists] |