From: Rick Haines <rick@kuroyi.net>
To: davidm@hpl.hp.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: read latency (ia64)
Date: Fri, 19 Apr 2002 18:10:26 -0400 [thread overview]
Message-ID: <20020419221026.GA1995@sasami.kuroyi.net> (raw)
In-Reply-To: <20020418140622.GA31405@sasami.kuroyi.net> <15552.34913.686564.487970@napali.hpl.hp.com>
On Fri, Apr 19, 2002 at 02:13:05PM -0700, David Mosberger wrote:
> >>>>> On Thu, 18 Apr 2002 10:06:22 -0400, Rick Haines <rick@kuroyi.net> said:
>
> Rick> I have a Lion with 4 666mhz B3 stepping cpus and 4GB ram
> Rick> running Debian unstable with kernel 2.4.18 and the 020410 ia64
> Rick> patch (I have the same problem with 2.4.9-itanium-smp from the
> Rick> archive).
>
> Rick> I have a program that reads large files in increments of 81920
> Rick> blocks. After about 9600 read calls I get about a dozen reads
> Rick> that take about 3 seconds each. Does anyone have any ideas as
> Rick> to a cause/solution? (I have 4 other threads working/possibly
> Rick> writing output at the same time, although in this case only 1
> Rick> of them would be active at the same time). I am also running
> Rick> a program that callocs almost all my ram to make sure none of
> Rick> the file is cached.
>
> I don't think anyone will be able to help you without a test case.
> Do you have a minimal test case that reproduces the problem?
I got a response from Andrew Morton that sounds promising. He says
it's probably that "writeback has kicked in, and your reads are stalling
behind the writes". I'll send another email after I try his patch.
--
Rick (rick@kuroyi.net)
http://dxr3.sourceforge.net
I think the slogan of the fansubbers puts
it best: "Cheaper than crack, and lots more fun."
prev parent reply other threads:[~2002-04-19 22:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-18 14:06 Rick Haines
2002-04-19 21:13 ` David Mosberger
2002-04-19 22:10 ` Rick Haines [this message]
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=20020419221026.GA1995@sasami.kuroyi.net \
--to=rick@kuroyi.net \
--cc=davidm@hpl.hp.com \
--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
all inboxes | Powered by JetHome®