From: Andrew Morton <akpm@zip.com.au>
To: Roy Sigurd Karlsbakk <roy@karlsbakk.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: io scheduling / serializing io requests / readahead
Date: Wed, 05 Dec 2001 12:16:27 -0800 [thread overview]
Message-ID: <3C0E809B.49D659A4@zip.com.au> (raw)
In-Reply-To: <Pine.LNX.4.30.0112051824120.2754-100000@mustard.heime.net>
Roy Sigurd Karlsbakk wrote:
>
> hi
>
> Are there any ways to tell Linux to use some sort of readahead
> functionality that'll give me the ability to schedule I/O more loosely, so
> some 100 files can be read concurrently without ruining the system by
> seeking all the time?
There's a new system call sys_readhead() which may provide what you
want.
A simple alternative is to just cat each file, one at a time
onto /dev/null before the application starts up.
> I've tried to alter /proc/sys/vm/(min|max)-readahead, but it doesn't have
> any effect...
>
Yup. We covered that in the other thread.
prev parent reply other threads:[~2001-12-05 20:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-05 17:27 io scheduling / serializing io requests / readahead Roy Sigurd Karlsbakk
2001-12-05 20:16 ` Andrew Morton [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=3C0E809B.49D659A4@zip.com.au \
--to=akpm@zip.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=roy@karlsbakk.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.