From: Andrew Morton <akpm@osdl.org>
To: Nuno Silva <nuno.silva@vgertech.com>
Cc: ahuisman@cistron.nl, linux-kernel@vger.kernel.org
Subject: Re: READAHEAD
Date: Fri, 31 Oct 2003 00:03:08 -0800 [thread overview]
Message-ID: <20031031000308.75c574da.akpm@osdl.org> (raw)
In-Reply-To: <3FA212BD.3070408@vgertech.com>
Nuno Silva <nuno.silva@vgertech.com> wrote:
>
> >> Before, i never had to set readahead so high
> >> Please could you tell me, what is going on here ?
> >
> >
> > Lots of people have been reporting this. It's rather weird.
> >
>
> I know nothing about this but, FWIW, I think that what changed where the
> units. With 2.4 you specify sectors, with 2.6 you specify bytes.
>
> So, having -a8, in 2.4, is the same as having -a$((8*512)) [it's 4096
> :)], in 2.6.
>
No, everything seems OK. Both `hdparm -a' and `blockdev --setra' are
operating in units of 512 bytes.
next prev parent reply other threads:[~2003-10-31 8:01 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-30 19:23 READAHEAD age
2003-10-30 21:44 ` READAHEAD Andrew Morton
2003-10-31 7:43 ` READAHEAD Nuno Silva
2003-10-31 8:03 ` Andrew Morton [this message]
2003-10-31 12:20 ` READAHEAD age
2003-10-31 9:28 ` READAHEAD Andrew Morton
2003-10-31 9:29 ` READAHEAD Andrew Morton
2003-11-01 9:15 ` READAHEAD age
2003-11-03 0:15 ` READAHEAD Derek Foreman
-- strict thread matches above, loose matches on Subject: below --
2005-09-27 2:38 Readahead Alan Stern
2005-09-27 3:06 ` Readahead Randy.Dunlap
2005-09-27 4:24 ` Readahead Andrew Morton
2005-09-28 18:40 ` Readahead Alan Stern
2003-11-01 17:22 READAHEAD Voluspa
2002-04-16 20:21 readahead Andries.Brouwer
2002-04-16 19:10 readahead Andries.Brouwer
2002-04-16 19:23 ` readahead Andrew Morton
2002-04-16 19:33 ` readahead Jens Axboe
2002-04-16 13:54 readahead Andries.Brouwer
2002-04-16 16:08 ` readahead Steven Cole
2002-04-16 18:25 ` readahead Andrew Morton
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=20031031000308.75c574da.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=ahuisman@cistron.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.silva@vgertech.com \
/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;
as well as URLs for NNTP newsgroup(s).