From: Namhyung Kim <namhyung@gmail.com>
To: Tejun Heo <tj@kernel.org>
Cc: dm-devel@redhat.com, Steven Rostedt <rostedt@goodmis.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH for-3.3/core] block: add missing block_bio_complete() tracepoint
Date: Sat, 18 Feb 2012 12:31:54 +0900 [thread overview]
Message-ID: <1329535914.1630.4.camel@leonhard> (raw)
In-Reply-To: <20120217211958.GG29414@google.com>
Hi,
2012-02-17, 13:19 -0800, Tejun Heo:
> bio completion didn't kick block_bio_complete TP. Only dm was
> explicitly triggering the TP on IO completion. This makes
> block_bio_complete TP useless for tracers which want to know about
> bios, and all other bio based drivers skip generating blktrace
> completion events.
>
> This patch makes all bio completions via bio_endio() generate
> block_bio_complete TP.
>
> * Explicit trace_block_bio_complete() invocation removed from dm and
> the trace point is unexported.
>
> * @rq dropped from trace_block_bio_complete(). bios may fly around
> w/o queue associated. Verifying and accessing the assocaited queue
> belongs to TP probes.
>
> * blktrace now gets both request and bio completions. Make it ignore
> bio completions if request completion path is happening.
>
> This makes all bio based drivers generate blktrace completion events
> properly and makes the block_bio_complete TP actually useful.
>
> Signed-off-by: Tejun Heo <tj@kernel.org>
> Original-patch-by: Namhyung Kim <namhyung@gmail.com>
> Cc: Tejun Heo <tj@kernel.org>
> Cc: Steven Rostedt <rostedt@goodmis.org>
> Cc: dm-devel@redhat.com
Looks better to me, thanks. :)
--
Regards,
Namhyung Kim
prev parent reply other threads:[~2012-02-18 3:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-17 21:19 [PATCH for-3.3/core] block: add missing block_bio_complete() tracepoint Tejun Heo
2012-02-17 21:19 ` Tejun Heo
2012-02-18 3:31 ` Namhyung Kim [this message]
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=1329535914.1630.4.camel@leonhard \
--to=namhyung@gmail.com \
--cc=dm-devel@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=tj@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 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.