From: Nick Piggin <piggin@cyberone.com.au>
To: Steven Pratt <slpratt@austin.ibm.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.5.70-mm2 causes performance drop of random read O_DIRECT
Date: Tue, 10 Jun 2003 10:13:30 +1000 [thread overview]
Message-ID: <3EE522AA.7020200@cyberone.com.au> (raw)
In-Reply-To: <3EE5190D.3070401@austin.ibm.com>
Steven Pratt wrote:
> Starting in 2.5.70-mm2 and continuing in the mm tree, there is a
> significant degrade in random read for block devices using O_DIRECT.
> The drop occurs for all block sizes and ranges from 30%-40. CPU usage
> is also lower although it may already be so low as to be irrelavent.
Hi Steven, this is quite likely to be an io scheduler problem.
Is your test program rawread v2.1.5? What is the command line
you are using to invoke the program?
next prev parent reply other threads:[~2003-06-10 0:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-09 23:32 2.5.70-mm2 causes performance drop of random read O_DIRECT Steven Pratt
2003-06-10 0:13 ` Nick Piggin [this message]
2003-06-10 14:05 ` Steven Pratt
2003-06-11 1:00 ` Nick Piggin
2003-06-11 15:16 ` Steven Pratt
2003-06-12 1:14 ` Nick Piggin
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=3EE522AA.7020200@cyberone.com.au \
--to=piggin@cyberone.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=slpratt@austin.ibm.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