The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Jesse Barnes <jbarnes@engr.sgi.com>
Cc: linux-kernel@vger.kernel.org, jeremy@sgi.com
Subject: Re: Buffered I/O slowness
Date: Fri, 29 Oct 2004 17:30:45 -0700	[thread overview]
Message-ID: <20041029173045.32722ac0.akpm@osdl.org> (raw)
In-Reply-To: <200410291716.25277.jbarnes@engr.sgi.com>

Jesse Barnes <jbarnes@engr.sgi.com> wrote:
>
> > I'm not sure that we know what's going on yet.  I certainly don't.  The
> > above numbers look good, so what's the problem???
> 
> The numbers are ~1/3 of what the machine is capable of with direct I/O.

Are there CPU cycles to spare?  If you have just one CPU copying 1GB/sec
out of pagecache, maybe it is pegged?

  reply	other threads:[~2004-10-30  0:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-26  1:14 Buffered write slowness Jesse Barnes
2004-10-29 17:46 ` Buffered I/O slowness Jesse Barnes
2004-10-29 23:08   ` Andrew Morton
2004-10-30  0:16     ` Jesse Barnes
2004-10-30  0:30       ` Andrew Morton [this message]
2004-11-01 18:26         ` Jesse Barnes
2004-11-01 18:34           ` Jesse Barnes

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=20041029173045.32722ac0.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=jbarnes@engr.sgi.com \
    --cc=jeremy@sgi.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