public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrea Arcangeli <andrea@suse.de>
To: Andrew Morton <akpm@digeo.com>
Cc: Felix von Leitner <felix-kernel@fefe.de>, linux-kernel@vger.kernel.org
Subject: Re: need better I/O scheduler for bulk file serving
Date: Mon, 19 May 2003 00:38:31 +0200	[thread overview]
Message-ID: <20030518223831.GD1429@dualathlon.random> (raw)
In-Reply-To: <20030518140642.64c7d619.akpm@digeo.com>

On Sun, May 18, 2003 at 02:06:42PM -0700, Andrew Morton wrote:
> Felix von Leitner <felix-kernel@fefe.de> wrote:
> >
> > Larger read-ahead maybe?
> 
> Or an anticipatory scheduler.  You don't say what kernel you're
> using.

yes, IMHO he could give a spin to my tree with better readahead and see
if it helps.

Andrea

  reply	other threads:[~2003-05-18 22:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-18 19:59 need better I/O scheduler for bulk file serving Felix von Leitner
2003-05-18 21:06 ` Andrew Morton
2003-05-18 22:38   ` Andrea Arcangeli [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-05-19  3:35 Chuck Ebbert
2003-05-19  3:51 ` Joel Jaeggli

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=20030518223831.GD1429@dualathlon.random \
    --to=andrea@suse.de \
    --cc=akpm@digeo.com \
    --cc=felix-kernel@fefe.de \
    --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