From: Linda Walsh <lkml@tlinx.org>
To: Jan Blunck <jblunck@suse.de>
Cc: linux-btrace@vger.kernel.org, Linux-Xfs <linux-xfs@oss.sgi.com>
Subject: Re: blktrace & btrace usability
Date: Tue, 22 Jan 2008 20:00:38 +0000 [thread overview]
Message-ID: <47964B66.5020001@tlinx.org> (raw)
In-Reply-To: <20080122164145.GB4531@hasse.suse.de>
Jan Blunck wrote:
> blktrace is used by the preload package. The preload package is capable of
> remapping blocks for faster booting. Therefore we need the blktrace
> output. But we only have a remapper for ext3.
>
----
I wondered about that, but the blktrace package doesn't containg
any utility for remapping blocks. The blktrace-0.99.3-12 package
included in OSuse-10.3, I only see utilities "blkparse, blktrace, btrace,
blkrawverify, btt, and verify_blktrace".
Was it left out by accident? ---or---
If the remapping is in a separate package, then shouldn't
the blktrace package "just" do the block tracing, regardless
of file type (i.e. in typical unix fashion, it does its part, and
another util (a block-re-arranger) does its part...?
Having blktrace do it's thing no matter what filesystem
follows might encourage or enable someone to write re-arrangers
for other filesystems...(?) After all, xfs already has
one block-rearranger program (for what little it is needed)
in "xfs_fsr". Does ext3 have something similar now?
Was the ext3 block re-arranging tool supposed to be
in the blktrace package?
thanks,
linda
next prev parent reply other threads:[~2008-01-22 20:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-18 8:38 blktrace & btrace usability Linda Walsh
2008-01-18 9:08 ` Jens Axboe
2008-01-18 22:31 ` Linda Walsh
2008-01-20 20:02 ` Jens Axboe
2008-01-22 16:41 ` Jan Blunck
2008-01-22 20:00 ` Linda Walsh [this message]
2008-01-23 13:27 ` Jan Blunck
2008-01-23 23:17 ` Linda Walsh
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=47964B66.5020001@tlinx.org \
--to=lkml@tlinx.org \
--cc=jblunck@suse.de \
--cc=linux-btrace@vger.kernel.org \
--cc=linux-xfs@oss.sgi.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).