From: Li Zefan <lizf@cn.fujitsu.com>
To: Ryo Tsuruta <ryov@valinux.co.jp>
Cc: Alan.Brunelle@hp.com, dm-devel@redhat.com,
linux-kernel@vger.kernel.org, jens.axboe@oracle.com,
mingo@elte.hu, rostedt@goodmis.org, fweisbec@gmail.com
Subject: Re: [RFC PATCH dm-ioband] Added in blktrace msgs for dm-ioband
Date: Wed, 13 May 2009 08:56:13 +0800 [thread overview]
Message-ID: <4A0A1AAD.3090606@cn.fujitsu.com> (raw)
In-Reply-To: <20090512.191206.226779551.ryov@valinux.co.jp>
>>>>>> Thanks for your suggestion. I'll use TRACE_EVENT instead.
>>>>> blk_add_trace_msg() supports both blktrace and tracepoints. I can
>>>>> get messages from dm-ioband through debugfs. Could you expain why
>>>>> should we use TRACE_EVENT instead?
>>>>>
>>>> Actually blk_add_trace_msg() has nothing to do with tracepoints..
>>>>
>>>> If we use blk_add_trace_msg() is dm, we can use it in md, various block
>>>> drivers and even ext4. So the right thing is, if a subsystem wants to add
>>>> trace facility, it should use tracepoints/TRACE_EVENT.
>>>>
>>>> With TRACE_EVENT, you can get output through debugfs too, and it can be used
>>>> together with blktrace:
>>>>
>>>> # echo 1 > /sys/block/dm/trace/enable
>>>> # echo blk > /debugfs/tracing/current_tracer
>>>> # echo dm-ioband-foo > /debugfs/tracing/tracing/set_event
>>>> # cat /deubgfs/tracing/trace_pipe
>>>>
>>>> And you can enable dm-ioband-foo while disabling dm-ioband-bar, and you can
>>>> use filter feature too.
>>> Thanks for explaining.
>>> The base kernel of current dm tree (2.6.30-rc4) has not supported
>>> dm-device tracing yet. I'll consider using TRACE_EVENT when the base
>>> kernel supports dm-device tracing.
>>>
>> I think we don't have any plan on dm-device tracing support, do we? And you
>> don't need that.
>>
>> I downloaded dm-ioband 1.10.4, and applied it to latest tip-tree, and made
>> a patch to convert those blktrace msgs to trace events.
>>
>> # ls /debug/tracing/events/dm-ioband
>> enable ioband_endio ioband_issue_list ioband_urgent_bio
>> filter ioband_hold_bio ioband_make_request
>> # echo 1 /debug/tracing/events/dm-ioband/enable
>> # echo blk /debug/tracing/current_tracer
>> ...
>
> Is the following line unnecessary in the latest tip-tree?
>
> # echo 1 > /sys/block/dm/trace/enable
>
Yes, still needed. I was not giving a complete demonstration. ;)
> How to enable/disable tracing on each device?
echo 1 > /sys/block/dm-0/trace/enable
echo 1 > /sys/block/dm-1/trace/enable
Or use filter facility:
echo "dev == $(( (ma0 << 20) | mi0 ))" > /debug/tracing/events/dm-ioband/filter
This will filter out all events generated from dm-1, leaving those from dm-0.
next prev parent reply other threads:[~2009-05-13 0:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-24 21:47 [RFC PATCH dm-ioband] Added in blktrace msgs for dm-ioband Alan D. Brunelle
2009-04-27 9:44 ` Ryo Tsuruta
2009-05-04 3:24 ` Li Zefan
2009-05-07 0:23 ` Ryo Tsuruta
2009-05-11 10:31 ` Ryo Tsuruta
2009-05-12 3:49 ` Li Zefan
2009-05-12 6:11 ` Ryo Tsuruta
2009-05-12 8:10 ` Li Zefan
2009-05-12 10:12 ` Ryo Tsuruta
2009-05-13 0:56 ` Li Zefan [this message]
2009-05-13 11:30 ` Ryo Tsuruta
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=4A0A1AAD.3090606@cn.fujitsu.com \
--to=lizf@cn.fujitsu.com \
--cc=Alan.Brunelle@hp.com \
--cc=dm-devel@redhat.com \
--cc=fweisbec@gmail.com \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.org \
--cc=ryov@valinux.co.jp \
/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