From: Mike Fedyk <mfedyk@matchmail.com>
To: Andrew Morton <akpm@zip.com.au>
Cc: Dieter N?tzel <Dieter.Nuetzel@hamburg.de>,
Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: Unresponiveness of 2.4.16
Date: Tue, 27 Nov 2001 18:34:29 -0800 [thread overview]
Message-ID: <20011127183429.B862@mikef-linux.matchmail.com> (raw)
In-Reply-To: <20011128013129Z281843-17408+21534@vger.kernel.org> <3C044855.3CF2DCA3@zip.com.au>
In-Reply-To: <3C044855.3CF2DCA3@zip.com.au>
On Tue, Nov 27, 2001 at 06:13:41PM -0800, Andrew Morton wrote:
> Dieter N?tzel wrote:
> > Don't forget to tune max-readahead.
>
> Yes. Readahead is fairly critical and there may be additional fixes
> needed in this area.
>
> Someone recently added the /proc/sys/vm/max_readahead (?) tunable.
> Beware of this. It only works for device drivers which do not
> populate their own readhead table. For IDE, it *looks* like
> it works, but it doesn't. For IDE, the only way to alter VM
> readahead is via
>
> echo file_readahead:N > /proc/ide/ide0/hda/settings
>
> where N is in kilobytes in 2.4.16 kernels.
Any idea which drivers it will/won't work on? ie, "almost all ide" or
"almost none of the ide driers"?
>In earlier kernels
> it's kilopages (!).
Isn't this part of the max-readahead patch?
Does /proc/sys/vm/max_readahead affect scsi in any way?
What layer does /proc/sys/vm/max_readahead affect? Block? FS?
MF
next prev parent reply other threads:[~2001-11-28 2:34 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-28 1:31 Unresponiveness of 2.4.16 Dieter Nützel
2001-11-28 2:13 ` Andrew Morton
2001-11-28 2:34 ` Mike Fedyk [this message]
2001-11-28 2:48 ` Andrew Morton
2001-11-28 20:21 ` Roger Larsson
2001-11-28 3:53 ` Dieter Nützel
[not found] ` <200111280353.fAS3rEB05638@zero.tech9.net>
2001-11-28 4:14 ` Robert Love
-- strict thread matches above, loose matches on Subject: below --
2001-11-28 19:42 Torrey Hoffman
2001-11-28 20:51 ` Dieter Nützel
2001-11-28 18:56 Torrey Hoffman
2001-11-28 19:31 ` Andrew Morton
2001-11-28 0:33 Torrey Hoffman
2001-11-28 0:48 ` Andrew Morton
2001-11-28 18:09 ` Marcelo Tosatti
2001-11-28 19:38 ` Andrew Morton
2001-11-27 9:56 willy tarreau
2001-11-27 10:57 ` Heinz Diehl
2001-11-26 22:02 Nathan G. Grennan
2001-11-26 22:17 ` Alan Cox
2001-11-26 23:34 ` Nicolas Pitre
2001-11-27 0:05 ` Steve Lion
2001-11-27 9:12 ` Ahmed Masud
2001-11-27 17:12 ` Andrew Morton
2001-11-27 20:31 ` Mike Fedyk
2001-11-27 20:57 ` Andrew Morton
2001-11-27 21:19 ` Martin Eriksson
2001-11-27 21:24 ` Mike Fedyk
2001-11-28 18:24 ` Marcelo Tosatti
2001-11-28 18:57 ` Marcelo Tosatti
2001-11-28 20:31 ` Andrew Morton
2001-11-28 20:56 ` Andreas Dilger
2001-11-28 21:12 ` Andrew Morton
2001-11-28 20:04 ` Marcelo Tosatti
2001-11-28 21:26 ` Andrew Morton
2001-11-26 23:59 ` Rik van Riel
2001-11-27 0:36 ` Andrew Morton
2001-11-27 0:46 ` Rik van Riel
2001-11-27 4:38 ` Mike Fedyk
2001-11-27 4:45 ` Andrew Morton
2001-11-27 1:45 ` Andrea Arcangeli
2001-11-26 22:21 ` Andrew Morton
2001-11-27 7:42 ` Jens Axboe
2001-11-27 7:58 ` Mike Fedyk
2001-11-27 8:01 ` Jens Axboe
2001-11-27 8:31 ` Andrew Morton
2001-11-27 8:38 ` Jens Axboe
2001-11-26 22:44 ` Lincoln Dale
2001-11-27 4:34 ` GOTO Masanori
2001-11-27 0:44 ` Lost Logic
2001-11-27 0:57 ` Lost Logic
2001-11-27 3:49 ` Sean Elble
2001-11-27 3:56 ` Doug Ledford
2001-11-27 4:00 ` Sean Elble
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=20011127183429.B862@mikef-linux.matchmail.com \
--to=mfedyk@matchmail.com \
--cc=Dieter.Nuetzel@hamburg.de \
--cc=akpm@zip.com.au \
--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