On Mon, Feb 18, 2008 at 03:22:02PM -0800, Linda Walsh wrote:
> Not to look excessively dumb, but what's xfsaild?
AIL = Active Item List
It is a sorted list all the logged metadata objects that have not
yet been written back to disk. The xfsaild is responsible for tail
pushing the log. i.e. writing back objects in the AIL in the most
efficient manner possible.
Why a thread? Because allowing parallelism in tail pushing is a
scalability problem and moving this to it's own thread completely
isolates it from parallelism. Tail pushing only requires a small
amount of CPU time, but it requires a global scope spinlock.
Isolating the pushing to a single CPU means the spinlock is not
contended across every CPU in the machine.
How much did it improve scalability? on a 2048p machine with an
MPI job that did a synchronised close of 12,000 files (6 per CPU),
the close time went from ~5400s without the thread to 9s with the
xfsaild. That's only about 600x faster. ;)
> xfs seems to be sprouting daemons at a more rapid pace
> these days...xfsbufd, xfssyncd, xfsdatad, xfslogd, xfs_mru_cache, and
> now xfsaild?
Why not? Got to make use of all those cores machines have these
Fundamentally, threads are cheap and simple. We'll keep adding
threads where it makes sense as long as it improves performance and
> 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.
'git log' is your friend. The commits that introduce the new threads
explain why they are necessary. ;)
SGI Australian Software Group