From: Jens Axboe <jens.axboe@oracle.com>
To: linux-btrace@vger.kernel.org
Subject: Re: [patch 0/2] blkparse extensions for PC requests
Date: Fri, 11 Jan 2008 09:10:35 +0000 [thread overview]
Message-ID: <20080111091035.GK6258@kernel.dk> (raw)
In-Reply-To: <20080107075057.066746000@de.ibm.com>
On Mon, Jan 07 2008, Christof Schmitt wrote:
> As a follow-up to the blktrace extension for SCSI generic device
> files, here are two patches that extend the tracing of PC requests in
> blkparse. When tracing I/O to SCSI tape drives, the I/O trace only
> contains PC requests. These extensions allow to get some more data
> from these traces.
Patches look fine, however should it just not default do this
accounting? But only print the status fields, if we actually saw a PC
request.
--
Jens Axboe
next prev parent reply other threads:[~2008-01-11 9:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-07 7:50 [patch 0/2] blkparse extensions for PC requests Christof Schmitt
2008-01-11 9:10 ` Jens Axboe [this message]
2008-01-14 6:38 ` Christof Schmitt
2008-01-14 7:53 ` 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=20080111091035.GK6258@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=linux-btrace@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).