From: Jeff Moyer <jmoyer@redhat.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: Tao Ma <tm@tao.ma>,
linux-kernel@vger.kernel.org,
Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [PATCH v2] blktrace: Don't output messages if NOTIFY isn't set.
Date: Wed, 19 Jan 2011 10:04:01 -0500 [thread overview]
Message-ID: <x49tyh5c4v2.fsf@segfault.boston.devel.redhat.com> (raw)
In-Reply-To: <4D36EA84.1000605@kernel.dk> (Jens Axboe's message of "Wed, 19 Jan 2011 06:43:32 -0700")
Jens Axboe <axboe@kernel.dk> writes:
> On 2011-01-18 23:09, Tao Ma wrote:
>> On 01/19/2011 01:36 PM, Jens Axboe wrote:
>>> On 2011-01-18 20:09, Tao Ma wrote:
>>>> Hi Jeff,
>>>> On 01/18/2011 11:50 PM, Jeff Moyer wrote:
>>>>> Tao Ma<tm@tao.ma> writes:
>>>>>
>>>>>> + /*
>>>>>> + * If the user does specify some action masks, don't send any note
>>>>>> + * message to the trace so that it won't pollute what the user really
>>>>>> + * want to see.
>>>>>> + */
>>>>>> + if (bt->act_mask != (u16) -1)
>>>>>> + return;
>>>>>> +
>>>>>
>>>>> I think you want to check for the BLK_TC_NOTIFY bit.
>>>> I was thinking of this, but actually there is no way for the user to set this flag.
>>>> At least from blktrace(8), -a doesn't have any flags like NOTIFY. So if the user
>>>> set any flag, NOTIFY will be cleared. So it does work. Thanks.
>>>>
>>>> Here is the updated patch.
>>>>
>>>> From 8693c19f165b09f60d5c26aed369d79a79e144ba Mon Sep 17 00:00:00 2001
>>>> From: Tao Ma<boyu.mt@taobao.com>
>>>> Date: Wed, 19 Jan 2011 10:51:44 +0800
>>>> Subject: [PATCH v2] blktrace: Don't output messages if NOTIFY isn't set.
>>>>
>>>> Now if we enable blktrace, cfq has too many messages output to the
>>>> trace buffer. It is fine if we don't specify any action mask.
>>>> But if I do like this:
>>>> blktrace /dev/sdb -a issue -a complete -o - | blkparse -i -
>>>> I only want to see 'D' and 'C', while with the following command
>>>> dd if=/mnt/ocfs2/test of=/dev/null bs=4k count=1 iflag=direct
>>>>
>>>> I will get(with a 2.6.37 vanilla kernel):
>>>> 8,16 0 0 0.000000000 0 m N cfq3805 alloced
>>>> 8,16 0 0 0.000004126 0 m N cfq3805 insert_request
>>>> 8,16 0 0 0.000004884 0 m N cfq3805 add_to_rr
>>>> 8,16 0 0 0.000008417 0 m N cfq workload slice:300
>>>> 8,16 0 0 0.000009557 0 m N cfq3805 set_active wl_prio:0 wl_type:2
>>>> 8,16 0 0 0.000010640 0 m N cfq3805 fifo= (null)
>>>> 8,16 0 0 0.000011193 0 m N cfq3805 dispatch_insert
>>>> 8,16 0 0 0.000012221 0 m N cfq3805 dispatched a request
>>>> 8,16 0 0 0.000012802 0 m N cfq3805 activate rq, drv=1
>>>> 8,16 0 1 0.000013181 3805 D R 114759 + 8 [dd]
>>>> 8,16 0 2 0.000164244 0 C R 114759 + 8 [0]
>>>> 8,16 0 0 0.000167997 0 m N cfq3805 complete rqnoidle 0
>>>> 8,16 0 0 0.000168782 0 m N cfq3805 set_slice=100
>>>> 8,16 0 0 0.000169874 0 m N cfq3805 arm_idle: 8 group_idle: 0
>>>> 8,16 0 0 0.000170189 0 m N cfq schedule dispatch
>>>> 8,16 0 0 0.000397938 0 m N cfq3805 slice expired t=0
>>>> 8,16 0 0 0.000399763 0 m N cfq3805 sl_used=1 disp=1 charge=1 iops=0 sect=8
>>>> 8,16 0 0 0.000400227 0 m N cfq3805 del_from_rr
>>>> 8,16 0 0 0.000400882 0 m N cfq3805 put_queue
>>>>
>>>> See, there are 19 lines while I only need 2. I don't think it is
>>>> appropriate for a user.
>>>>
>>>> So this patch will disable any messages if the BLK_TC_NOTIFY isn't set.
>>>> Now the output for the same command will look like:
>>>> 8,16 0 1 0.000000000 4908 D R 114759 + 8 [dd]
>>>> 8,16 0 2 0.000146827 0 C R 114759 + 8 [0]
>>>>
>>>> Yes, it is what I want to see.
>>>>
>>>> Cc: Jens Axboe<axboe@kernel.dk>
>>>> Cc: Steven Rostedt<rostedt@goodmis.org>
>>>> Cc: Jeff Moyer<jmoyer@redhat.com>
>>>> Signed-off-by: Tao Ma<boyu.mt@taobao.com>
>>>> ---
>>>> kernel/trace/blktrace.c | 7 +++++++
>>>> 1 files changed, 7 insertions(+), 0 deletions(-)
>>>>
>>>> diff --git a/kernel/trace/blktrace.c b/kernel/trace/blktrace.c
>>>> index 153562d..d95721f 100644
>>>> --- a/kernel/trace/blktrace.c
>>>> +++ b/kernel/trace/blktrace.c
>>>> @@ -138,6 +138,13 @@ void __trace_note_message(struct blk_trace *bt, const char *fmt, ...)
>>>> !blk_tracer_enabled))
>>>> return;
>>>>
>>>> + /*
>>>> + * If the BLK_TC_NOTIFY action mask isn't set, don't send any note
>>>> + * message to the trace.
>>>> + */
>>>> + if (!(bt->act_mask& BLK_TC_NOTIFY))
>>>> + return;
>>>> +
>>>> local_irq_save(flags);
>>>> buf = per_cpu_ptr(bt->msg_data, smp_processor_id());
>>>> va_start(args, fmt);
>>>
>>> Hmm, it should only mask messages, not task/timestamp notifies. This
>>> will mask all of them.
>> uh, yes, that's the reason why I put the check in __trace_note_message,
>> not in trace_note. trace_note_time and trace_note_tsk will handle
>> time/task issue and then call trace_note with the appropriate action
>> mask. Do I miss something here?
>
> You did, I missed that. Patch looks fine then, I'll queue it up. Thanks!
I was guessing at the use of BLK_TC_NOTIFY for this. Should there be
another flag for these messages, so they aren't conflated with
task/timestamp notifications?
Cheers,
Jeff
next prev parent reply other threads:[~2011-01-19 15:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-18 6:43 [PATCH] blktrace: Don't output messages if the user sets some action mask Tao Ma
2011-01-18 15:50 ` Jeff Moyer
2011-01-19 3:09 ` [PATCH v2] blktrace: Don't output messages if NOTIFY isn't set Tao Ma
2011-01-19 5:36 ` Jens Axboe
2011-01-19 6:09 ` Tao Ma
2011-01-19 13:43 ` Jens Axboe
2011-01-19 15:04 ` Jeff Moyer [this message]
2011-01-19 15:06 ` Jens Axboe
2011-01-19 15:13 ` Tao Ma
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=x49tyh5c4v2.fsf@segfault.boston.devel.redhat.com \
--to=jmoyer@redhat.com \
--cc=axboe@kernel.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=tm@tao.ma \
/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
all inboxes | Powered by JetHome®