public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: Christian Volkmann <haveaniceday@cv-sv.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Does a kernel assisted file system reorder make sense?
Date: Sun, 15 Nov 2009 14:37:28 +0100	[thread overview]
Message-ID: <87bpj36h9j.fsf@basil.nowhere.org> (raw)
In-Reply-To: <4AFFDA7C.6010907@cv-sv.de> (Christian Volkmann's message of "Sun, 15 Nov 2009 11:39:56 +0100")

Christian Volkmann <haveaniceday@cv-sv.de> writes:

> Hi,
>
> I just have read some articles about faster booting systems
> (Ubuntu 9.10) , SSD, hard disks, latency and seek times...
>
> Due to this I have some ideas which I like to discuss.
> I am for sure not the first with this idea, but I do not
> find any discussion about it. :)

Most modern distributions these days use some variant of prefetch at
boot.

> Shouldn't it be possible for the kernel to provide an ordered
> loaded block list read from disk ? This could be used for a kind
> of "forced reorder" for a file system tool.

Typically it's enough to just collect all the blocks read at boot and
then prefetch them in order to minimize seeks. That's what various
distributions do, typically by using blktrace to generate these lists
and then suitable prefetch daemons. Sometimes it's also just done at
the file level, because that's often also good enough.

The suse preload package also has a e2remapblocks for remapping inside
individual files, but I don't think it helps all that much. At least
it's not used by default.

-Andi


-- 
ak@linux.intel.com -- Speaking for myself only.

      parent reply	other threads:[~2009-11-15 13:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-15 10:39 Does a kernel assisted file system reorder make sense? Christian Volkmann
2009-11-15 11:38 ` Alexander Clouter
2009-11-15 13:37 ` Andi Kleen [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=87bpj36h9j.fsf@basil.nowhere.org \
    --to=andi@firstfloor.org \
    --cc=haveaniceday@cv-sv.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