From: Jens Axboe <jens.axboe@oracle.com>
To: "Alan D. Brunelle" <Alan.Brunelle@hp.com>
Cc: btrace <linux-btrace@vger.kernel.org>,
dm-devel@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Fix remap handling by blktrace
Date: Tue, 07 Aug 2007 13:32:52 +0000 [thread overview]
Message-ID: <20070807133252.GY5245@kernel.dk> (raw)
In-Reply-To: <46B87357.8040802@hp.com>
On Tue, Aug 07 2007, Alan D. Brunelle wrote:
>
>
> This patch provides more information concerning REMAP operations on block
> IOs. The additional information provides clearer details at the user level,
> and supports post-processing analysis in btt.
>
> o Adds in partition remaps on the same device.
> o Fixed up the remap information in DM to be in the right order
> o Sent up mapped-from and mapped-to device information
>
> Signed-off-by: Alan D. Brunelle <alan.brunelle@hp.com>
Thanks (again) Alan, applied!
--
Jens Axboe
next prev parent reply other threads:[~2007-08-07 13:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-07 13:27 [PATCH] Fix remap handling by blktrace Alan D. Brunelle
2007-08-07 13:32 ` Jens Axboe [this message]
2007-08-13 12:16 ` Jens Axboe
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=20070807133252.GY5245@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=Alan.Brunelle@hp.com \
--cc=dm-devel@redhat.com \
--cc=linux-btrace@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).