All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bart Samwel <bart@samwel.tk>
To: Andrew Morton <akpm@osdl.org>
Cc: felix-kernel@fefe.de, linux-kernel@vger.kernel.org
Subject: Re: Request: I/O request recording
Date: Tue, 27 Jan 2004 20:13:54 +0100	[thread overview]
Message-ID: <4016B872.3090309@samwel.tk> (raw)
In-Reply-To: <20040125153803.4d7e1015.akpm@osdl.org>

Andrew Morton wrote:
> You could certainly do that.  Given disk block #N you need to search all
> files on the disk asking "who owns this block".  The FIBMAP ioctl can be
> used on most filesystems (ext2, ext3, others..) to find out which blocks a
> file is using.   See bmap.c in
> 
> http://www.zip.com.au/~akpm/linux/patches/stuff/ext3-tools.tar.gz
> 
> Unfortunately you cannot determine a directory's blocks in this way. 
> Ext3's directories live in the /dev/hda1 pagecache anyway.  ext2's
> directories each have their own pagecache.

OK, I've written something that does this (but only correctly for ext3). 
I've put it here:

http://www.xs4all.nl/~bsamwel/bootup_prefetch.tar.gz

I haven't had the opportunity to do good measurements, so I don't really 
know if it even increases performance. If anyone feels like benchmarking 
this, I'd be very happy to hear from you. I don't really expect 
performance increases, as the bootup scripts seem to have enough 
processing to do to keep the system busy even without disk I/O. I wonder 
if it might make a difference on a faster processor though, my system's 
kind of sluggish by today's standards.

-- Bart

      parent reply	other threads:[~2004-01-27 19:16 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-24 18:10 Request: I/O request recording Felix von Leitner
2004-01-24 18:23 ` Valdis.Kletnieks
2004-01-24 18:26 ` Arjan van de Ven
2004-01-24 19:25   ` Ville Herva
2004-01-24 22:43     ` Arjan van de Ven
2004-01-24 20:11 ` Diego Calleja
2004-01-24 21:09   ` Ville Herva
2004-01-24 23:35 ` Andrew Morton
2004-01-24 23:53   ` Davide Libenzi
2004-01-25  0:03     ` Andrew Morton
2004-01-25  0:09       ` Davide Libenzi
2004-01-25  0:04     ` Valdis.Kletnieks
2004-01-25  0:10       ` Davide Libenzi
2004-01-25 12:26     ` Felipe Alfaro Solana
2004-01-25 22:59   ` Bart Samwel
2004-01-25 23:09     ` Andrew Morton
2004-01-25 23:29       ` Bart Samwel
2004-01-25 23:38         ` Andrew Morton
2004-01-26  0:23           ` Diego Calleja García
2004-01-26  0:32             ` Andrew Morton
2004-01-26 11:50           ` Bart Samwel
2004-01-26 11:57             ` Andrew Morton
2004-01-27 19:13           ` Bart Samwel [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=4016B872.3090309@samwel.tk \
    --to=bart@samwel.tk \
    --cc=akpm@osdl.org \
    --cc=felix-kernel@fefe.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 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.