From: Christoph Hellwig <hch@infradead.org>
To: Jeff Moyer <jmoyer@redhat.com>
Cc: Christoph Hellwig <hch@infradead.org>,
"Dan J. Williams" <dan.j.williams@intel.com>,
linux-nvdimm@ml01.01.org, linux-block@vger.kernel.org
Subject: Re: [patch] nd_blk,nd_pmem,nd_btt: add endio blktrace events
Date: Thu, 10 Nov 2016 11:33:33 -0800 [thread overview]
Message-ID: <20161110193333.GA10865@infradead.org> (raw)
In-Reply-To: <x49inrwo2v5.fsf@segfault.boston.devel.redhat.com>
On Wed, Nov 09, 2016 at 02:43:58PM -0500, Jeff Moyer wrote:
> But on the issue side, we have different trace actions: Q vs. I. On the
> completion side, we just have C. You'd end up getting two C events for
> each Q, and that may confuse existing utilities (such as blkparse, btt,
> iowatcher, fio, etc), not to mention any scripts built around the
> tracepoints, and any users looking at the raw blkparse output.
>
> So, are you suggesting we add another action on the endio side? If so,
> that's a different patch set. ;-) If you're suggesting this multiple C
> event thing, I'm not on board with that.
Ok, good point. It's a little bit annoying how asymetic the tracepoints
are, but fixing it now might cause more harm than it helps.
That being said, it might still be a good idea to have bio_endio call
the tracepoint, we'll just need a __bio_endio to bypass the tracepoints
for calls from the request layer. That way all bio-based drivers will
automatically do the right thing.
next prev parent reply other threads:[~2016-11-10 19:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-09 19:08 [patch] nd_blk,nd_pmem,nd_btt: add endio blktrace events Jeff Moyer
[not found] ` <x49twbgo4i6.fsf-RRHT56Q3PSP4kTEheFKJxxDDeQx5vsVwAInAS/Ez/D0@public.gmane.org>
2016-11-09 19:17 ` Christoph Hellwig
2016-11-09 19:31 ` Jeff Moyer
[not found] ` <x49mvh8o3fx.fsf-RRHT56Q3PSP4kTEheFKJxxDDeQx5vsVwAInAS/Ez/D0@public.gmane.org>
2016-11-09 19:34 ` Christoph Hellwig
2016-11-09 19:43 ` Jeff Moyer
2016-11-10 19:33 ` Christoph Hellwig [this message]
2016-11-11 14:55 ` Jeff Moyer
2016-11-16 4:56 ` Ross Zwisler
2016-11-16 14:06 ` Jeff Moyer
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=20161110193333.GA10865@infradead.org \
--to=hch@infradead.org \
--cc=dan.j.williams@intel.com \
--cc=jmoyer@redhat.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvdimm@ml01.01.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).