On Mon, May 02, 2011 at 09:04:40PM -0700, Christian Kujau wrote:
> On Tue, 3 May 2011 at 10:51, Dave Chinner wrote:
> > Can you run an event trace of all the XFS events during a find for
> > me? Don't do it over the entire subset of the filesystem - only
> You mean "event tracing", as in Documentation/trace/events.txt. For
> that I will have to enable CONFIG_FTRACE and CONFIG_FUNCTION_TRACER and
> probably others, right?
> Looking at http://lwn.net/Articles/341899, I see CONFIG_EVENT_TRACING
> and the way to enable event tracing for "all events in fs/xfs" would be:
> echo 1 > /sys/kernel/debug/tracing/events/xfs/enable
Download trace-cmd and use that - more efficient and easier to
specify the events to record...
> > 100,000 inodes is sufficient (i.e. kill the find once the xfs inode
> > cache slab reaches 100k inodes. While still running the event trace,
> > can you then drop the caches (echo 3 > /proc/sys/vm/drop_caches) and
> > check that the xfs inode cache is emptied? If it isn't emptied, drop
> > caches again to see if that empties it. If you coul dthen post the
> > event trace, I might be able to see what is going strange with the
> > shrinker and/or reclaim.
> Will try to do all that.
> I wonder why nobody else is affected by this. Because nobody else runs
> powerpc or UP any more? I'm sure other people's filesystems are way bigger
> than mine, with much more inodes to cache...
XFS on uniprocessor, 32 bit, highmem system is pretty rare. Let
alone on an old powerpc platform. It's so far out in left field that
I'd expect the only test coverage we get is your laptop....