From: Christoph Hellwig <hch@infradead.org>
To: Jeff Mahoney <jeffm@suse.com>
Cc: Mark Fasheh <mfasheh@suse.de>,
Christoph Hellwig <hch@infradead.org>,
xfs@oss.sgi.com
Subject: Re: xfs-trace-ilock-more
Date: Sun, 18 Dec 2011 15:26:51 -0500 [thread overview]
Message-ID: <20111218202651.GA20799@infradead.org> (raw)
In-Reply-To: <4EE8F7F0.7070207@suse.com>
On Wed, Dec 14, 2011 at 02:24:32PM -0500, Jeff Mahoney wrote:
> That's pretty much the explanation. With heavy reader load, buffered
> writes were stalling for 80 ms and sometimes longer. I suspected it
> was contention on the ilock and the tracing with that patch
> demonstrated a delay there. Since we were chasing a similar issue at
> another site, it seemed worthwhile to just keep it around. We're still
> tracking down the cause. I'm not sure if more recent kernels have the
> same issue as there's been quite a lot of churn.
Ok. I was a bit surprised that it was one out of only two XFS updates
that went into a recent SLES security errata, and I never heard about it
before.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2011-12-18 20:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-14 2:40 xfs-trace-ilock-more Christoph Hellwig
2011-12-14 18:27 ` xfs-trace-ilock-more Mark Fasheh
2011-12-14 19:24 ` xfs-trace-ilock-more Jeff Mahoney
2011-12-14 20:32 ` xfs-trace-ilock-more Dave Chinner
2011-12-14 22:42 ` xfs-trace-ilock-more Jeff Mahoney
2011-12-18 20:26 ` Christoph Hellwig [this message]
2011-12-18 20:27 ` xfs-trace-ilock-more Christoph Hellwig
2012-01-05 22:38 ` xfs-trace-ilock-more Mark Fasheh
2012-01-05 23:54 ` xfs-trace-ilock-more Dave Chinner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20111218202651.GA20799@infradead.org \
--to=hch@infradead.org \
--cc=jeffm@suse.com \
--cc=mfasheh@suse.de \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.