From: William Lee Irwin III <wli@holomorphy.com>
To: Judith Lebzelter <judith@osdl.org>
Cc: linux-aio@kvack.org, linux-kernel@vger.kernel.org, akpm@osdl.org
Subject: Re: OSDL aio-stress results on latest kernels show buffered random read issue
Date: Wed, 29 Sep 2004 17:44:47 -0700 [thread overview]
Message-ID: <20040930004447.GI9106@holomorphy.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0409291621170.4332-100000@osdlab.pdx.osdl.net>
On Wed, Sep 29, 2004 at 04:29:08PM -0700, Judith Lebzelter wrote:
> There seems to be an issue with the reads. Usually, reads
> should be at least as fast as writes of the same type.
> Also, there seems to be a substantial drop-off in the performance
> of AIO buffered-random writes in the mm kernels. (14% on 2CPU,
> 40% on 4CPU)
Okay, is it cpu time or idle/iowait? If it's cpu time, where do
profiles show it appears?
-- wli
next prev parent reply other threads:[~2004-09-30 0:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-29 23:29 OSDL aio-stress results on latest kernels show buffered random read issue Judith Lebzelter
2004-09-30 0:44 ` William Lee Irwin III [this message]
2004-09-30 22:00 ` Judith Lebzelter
2004-09-30 3:46 ` Andrew Morton
2004-09-30 17:48 ` Judith Lebzelter
2004-09-30 18:54 ` Bill Davidsen
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=20040930004447.GI9106@holomorphy.com \
--to=wli@holomorphy.com \
--cc=akpm@osdl.org \
--cc=judith@osdl.org \
--cc=linux-aio@kvack.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox