From: Suparna Bhattacharya <suparna@in.ibm.com>
To: Benjamin LaHaise <bcrl@kvack.org>
Cc: linux-aio@kvack.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: aio-stress throughput regressions from 2.6.11 to 2.6.12
Date: Wed, 6 Jul 2005 10:00:56 +0530 [thread overview]
Message-ID: <20050706043056.GA4223@in.ibm.com> (raw)
In-Reply-To: <20050701142555.GB31989@kvack.org>
On Fri, Jul 01, 2005 at 10:25:55AM -0400, Benjamin LaHaise wrote:
> On Fri, Jul 01, 2005 at 01:26:00PM +0530, Suparna Bhattacharya wrote:
> > On one test system I see a degradation from around 17+ MB/s to 11MB/s
> > for random O_DIRECT AIO (aio-stress -o3 testext3/rwfile5) from 2.6.11
> > to 2.6.12. It doesn't seem filesystem specific. Not good :(
>
> What sort of io subsystem does it have? Also, does changing the
aic7xxx.
> elevator make any difference? I'm away for the long weekend, but will
I tried switching to the noop elevator - the regression was still there.
> help look into this next week.
Do you see the regression as well, or is it just me ?
Regards
Suparna
>
> -ben
--
Suparna Bhattacharya (suparna@in.ibm.com)
Linux Technology Center
IBM Software Lab, India
next prev parent reply other threads:[~2005-07-06 5:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-01 7:56 aio-stress throughput regressions from 2.6.11 to 2.6.12 Suparna Bhattacharya
2005-07-01 7:56 ` Suparna Bhattacharya
2005-07-01 14:25 ` Benjamin LaHaise
2005-07-06 4:30 ` Suparna Bhattacharya [this message]
2005-07-08 17:58 ` Benjamin LaHaise
2005-07-08 17:58 ` Benjamin LaHaise
2005-07-05 14:00 ` Chris Mason
2005-07-05 14:00 ` Chris Mason
2005-07-05 16:12 ` Benjamin LaHaise
2005-07-05 16:12 ` Benjamin LaHaise
2005-07-06 10:37 ` Suparna Bhattacharya
2005-07-06 10:37 ` Suparna Bhattacharya
2005-07-06 12:10 ` aio-stress regressions in 2.6.12 narrowed down to AIC7xxx Suparna Bhattacharya
2005-07-11 7:43 ` aio-stress throughput regressions from 2.6.11 to 2.6.12 Sébastien Dugué
2005-07-11 7:43 ` Sébastien Dugué
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=20050706043056.GA4223@in.ibm.com \
--to=suparna@in.ibm.com \
--cc=bcrl@kvack.org \
--cc=linux-aio@kvack.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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.