linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kara <jack@suse.cz>
To: linux-fsdevel@vger.kernel.org
Subject: Ext2/3 block remapping tool
Date: Thu, 26 Apr 2007 21:29:53 +0200	[thread overview]
Message-ID: <20070426192953.GC2841@duck.suse.cz> (raw)

  Hello,

  I've been lately playing with remapping ext2/ext3 blocks (especially how
much it can give us in terms of speed of things like KDE start). For that
I've written two simple tools (you can get them from
ftp.suse.com/pub/people/jack/ext3remapper.tar.gz):
  e2block2file to transform (preparsed) output from blktrace into a list
of accessed files and offsets accessed
  e2remapblocks to use output from e2block2file and remap blocks into big
chunks in the order in which they were accessed.
  (see README in the tools archive for more details)

  So far the tools (especially e2remapblocks ;) work on unmounted
filesystem. The ultimate goal is to be able to do similar things for
mounted filesystems but I wanted to see whether block remapping is worth it
and what kernel interfaces would be useful for achieving the goal.
  BTW, the results for KDE startup are as follows:
The root partition was about 4.8 GB with around 1 GB free. System has
1GB mem. All measurements (except for warmcache) were performed after
  sync; echo 3 >/proc/sys/vm/drop_caches

Ordinary start: 19.2 20.3 19.5 19.8 19.3; avg. 19.62
Start with all data cached: 7 7.6 7.3 7.1 7.1; avg. 7.22
Start with fcache (see thread http://lkml.org/lkml/2006/5/15/46 for details
on fcache):
  11.3 11 10.3 10.8 10.6; avg. 10.8
Start with blocks remapped with e2remapblocks:
  13.5 15 13 14.5 14.5; avg. 14.1
(after remapping, data was stored in 20 continguous extents on disk)

								Honza


-- 
Jan Kara <jack@suse.cz>
SuSE CR Labs

             reply	other threads:[~2007-04-26 19:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-26 19:29 Jan Kara [this message]
2007-04-27 18:09 ` Ext2/3 block remapping tool Andreas Dilger
2007-04-30 10:12   ` Jan Kara
2007-04-30 12:09   ` Theodore Tso
2007-04-30 12:29     ` Jan Kara
2007-05-01  6:01     ` Andreas Dilger
2007-05-01 15:28       ` Theodore Tso
2007-05-01 18:52         ` Andreas Dilger
2007-05-01 22:18           ` Theodore Tso

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=20070426192953.GC2841@duck.suse.cz \
    --to=jack@suse.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).