From: Jens Axboe <axboe@kernel.dk>
To: Jeff Moyer <jmoyer@redhat.com>, linux-block@vger.kernel.org
Cc: agk@redhat.com, snitzer@redhat.com, dm-devel@redhat.com,
shli@kernel.org, linux-kernel@vger.kernel.org,
linux-raid@vger.kernel.org, hch@lst.de
Subject: Re: [patch] block: add blktrace C events for bio-based drivers
Date: Tue, 17 Jan 2017 14:07:32 -0800 [thread overview]
Message-ID: <f3044f42-3134-c577-068f-bd2750528b32@kernel.dk> (raw)
In-Reply-To: <x49ziips61y.fsf@segfault.boston.devel.redhat.com>
On 01/17/2017 01:57 PM, Jeff Moyer wrote:
> Only a few bio-based drivers actually generate blktrace completion
> (C) events. Instead of changing all bio-based drivers to call
> trace_block_bio_complete, move the tracing to bio_complete, and remove
> the explicit tracing from the few drivers that actually do it. After
> this patch, there is exactly one caller of trace_block_bio_complete
> and one caller of trace_block_rq_complete. More importantly, all
> bio-based drivers now generate C events, which is useful for
> performance analysis.
I like the change, hate the naming. I'd prefer one of two things:
- Add bio_endio_complete() instead. That name sucks too, the
important part is flipping the __name() to have a trace
version instead.
- Mark the bio as trace completed, and keep the naming. Since
it's only off the completion path, that can be just marking
the bi_flags non-atomically.
I probably prefer the latter.
--
Jens Axboe
next prev parent reply other threads:[~2017-01-17 22:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-17 21:57 [patch] block: add blktrace C events for bio-based drivers Jeff Moyer
2017-01-17 22:07 ` Jens Axboe [this message]
2017-01-17 22:39 ` Jeff Moyer
2017-01-18 16:01 ` 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=f3044f42-3134-c577-068f-bd2750528b32@kernel.dk \
--to=axboe@kernel.dk \
--cc=agk@redhat.com \
--cc=dm-devel@redhat.com \
--cc=hch@lst.de \
--cc=jmoyer@redhat.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=shli@kernel.org \
--cc=snitzer@redhat.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).