From: Christoph Hellwig <hch@infradead.org>
To: Joshua Aune <luken@fusionio.com>
Cc: Paul Saab <ps@fb.com>, "xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: Re: Performance regression between 2.6.32 and 2.6.38
Date: Sat, 10 Sep 2011 02:05:23 -0400 [thread overview]
Message-ID: <20110910060522.GA26968@infradead.org> (raw)
In-Reply-To: <F70D1B6A-0387-4646-B97B-98ED895F7759@fusionio.com>
On Fri, Sep 09, 2011 at 06:23:54PM -0600, Joshua Aune wrote:
> Are there any mount options or other tests that can be run in the failing configuration that would be helpful to isolate this further?
The best thing would be to bisect it down to at least a kernel release,
and if possible to a -rc or individual change (the latter might start
to get hard due to various instabilities in early -rc kernels)
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2011-09-10 6:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-10 0:23 Performance regression between 2.6.32 and 2.6.38 Joshua Aune
2011-09-10 6:05 ` Christoph Hellwig [this message]
2011-09-10 18:10 ` Paul Saab
2011-09-10 18:26 ` Christoph Hellwig
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=20110910060522.GA26968@infradead.org \
--to=hch@infradead.org \
--cc=luken@fusionio.com \
--cc=ps@fb.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox