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: Wed, 23 Jan 2008 23:17:30 +0000 [thread overview]
Message-ID: <4797CB0A.7050406@tlinx.org> (raw)
In-Reply-To: <20080123132700.GI4531@hasse.suse.de>
Jan Blunck wrote:
> On Tue, Jan 22, Linda Walsh wrote:
>
>
>> 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---
>>
>
> No, this is the reason why I said "blktrace is used by the preload
> package". The ext3remapper is part of the preload package.
>
----
Ahh...I'm sorry, I didn't know that the blktrace rc-scripts were
unrelated to the blktrace package and that by preload package you meant
a package named "preload" (I thought preload was some other phase
that I didn't know about that happened before other packages
were processed, or something). I got confused by the names (no
idea why...*cough*)... I'm not sure why the package, "preload", got
installed and "chkconfig'ed on" when I have no ext{23} disks.
I have "personal" issues with each new version adding more
automatically run "services". Reminds me more and more of WinXP with
all its auto-start boot progs & services and how it initially (pre-SP2),
installed with most services turned on (even though they weren't
needed by most users). In a similar way, SuSE organizes its
rpms to "require" features (packages) that I don't want and don't
need (avahi an apple-ad-hoc networking util with most of gnome
requiring its presence).
xfs has a file-system re-organizer, but its design goal
(probably ~10 years back) was simply to coalesce discontiguous
file parts to speed up speed sensitive real-time video streaming.
If it was deemed important, the existing xfs_fsr might be
adaptable...
Sorry for my confusion..., from the names "boot.blktrace" &
"stopblktrace", I thought they were general scripts for recording
the "boot+rc" block actions -- not specifically for the
package named "preload".
-l
WARNING: multiple messages have this Message-ID (diff)
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: Wed, 23 Jan 2008 15:17:30 -0800 [thread overview]
Message-ID: <4797CB0A.7050406@tlinx.org> (raw)
In-Reply-To: <20080123132700.GI4531@hasse.suse.de>
Jan Blunck wrote:
> On Tue, Jan 22, Linda Walsh wrote:
>
>
>> 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---
>>
>
> No, this is the reason why I said "blktrace is used by the preload
> package". The ext3remapper is part of the preload package.
>
----
Ahh...I'm sorry, I didn't know that the blktrace rc-scripts were
unrelated to the blktrace package and that by preload package you meant
a package named "preload" (I thought preload was some other phase
that I didn't know about that happened before other packages
were processed, or something). I got confused by the names (no
idea why...*cough*)... I'm not sure why the package, "preload", got
installed and "chkconfig'ed on" when I have no ext{23} disks.
I have "personal" issues with each new version adding more
automatically run "services". Reminds me more and more of WinXP with
all its auto-start boot progs & services and how it initially (pre-SP2),
installed with most services turned on (even though they weren't
needed by most users). In a similar way, SuSE organizes its
rpms to "require" features (packages) that I don't want and don't
need (avahi an apple-ad-hoc networking util with most of gnome
requiring its presence).
xfs has a file-system re-organizer, but its design goal
(probably ~10 years back) was simply to coalesce discontiguous
file parts to speed up speed sensitive real-time video streaming.
If it was deemed important, the existing xfs_fsr might be
adaptable...
Sorry for my confusion..., from the names "boot.blktrace" &
"stopblktrace", I thought they were general scripts for recording
the "boot+rc" block actions -- not specifically for the
package named "preload".
-l
next prev parent reply other threads:[~2008-01-23 23:17 UTC|newest]
Thread overview: 11+ 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
2008-01-22 20:00 ` Linda Walsh
2008-01-23 13:27 ` Jan Blunck
2008-01-23 13:27 ` Jan Blunck
2008-01-23 23:17 ` Linda Walsh [this message]
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=4797CB0A.7050406@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 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.