From: "Frantisek Rysanek" <Frantisek.Rysanek@post.cz>
To: linux-fsdevel@vger.kernel.org
Subject: Re: Disk IO, "Paralllel sequential" load: read-ahead inefficient? FS tuning?
Date: Fri, 10 Apr 2009 08:19:58 +0200 [thread overview]
Message-ID: <49DF012E.17197.988E1FE5@localhost> (raw)
In-Reply-To: <87prfl8zzk.fsf@basil.nowhere.org>
On 9 Apr 2009 at 20:05, Andi Kleen wrote:
[...]
> unsigned long max_sane_readahead(unsigned long nr)
[...]
> Wu Fengguang (cc'ed) is doing a lot of work on the MADV_* readahead
> algorithms. There was a recent new patchkit from him on linux-
kernel
[...]
> For example for faster booting sys_readahead() is widely used now.
>
Okay, thanks for the pointers :-)
Now I know where to get follow-up reading / try some hacking...
Frank Rysanek
prev parent reply other threads:[~2009-04-10 6:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-08 14:22 Disk IO, "Paralllel sequential" load: read-ahead inefficient? FS tuning? Frantisek Rysanek
2009-04-09 18:05 ` Andi Kleen
2009-04-10 2:35 ` Wu Fengguang
2009-04-10 6:19 ` Frantisek Rysanek [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=49DF012E.17197.988E1FE5@localhost \
--to=frantisek.rysanek@post.cz \
--cc=linux-fsdevel@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;
as well as URLs for NNTP newsgroup(s).