From: Ingo Molnar Date: Tue, 14 Apr 2009 08:38:56 +0000 Subject: Re: PATCH 1/3] blktrace: support per-partition tracing Message-Id: <20090414083856.GF27003@elte.hu> List-Id: References: <49E42620.4050701@cn.fujitsu.com> <20090414080919.GB27003@elte.hu> <49E448F6.5010506@cn.fujitsu.com> In-Reply-To: <49E448F6.5010506@cn.fujitsu.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Li Zefan Cc: Steven Rostedt , Tom Zanussi , Jens Axboe , Arnaldo Carvalho de Melo , Theodore Ts'o , Shawn Du , LKML , linux-btrace@vger.kernel.org * Li Zefan wrote: > Ingo Molnar wrote: > > * Li Zefan wrote: > > > >> From: Shawn Du > >> > >> Though one can specify '-d /dev/sda1' when using blktrace, it > >> still traces the whole sda. > >> > >> To support per-partition tracing, when we start tracing, we > >> initialize bt->start_lba and bt->end_lba to the start and end > >> sector of that partition. > >> > >> Note some actions are per device, thus we don't filter 0-sector > >> events. > >> > >> The original patch and discussion can be found here: > >> http://marc.info/?l=linux-btrace&m2949374214540&w=2 > >> > >> Signed-off-by: Shawn Du > >> Signed-off-by: Li Zefan > > > > Thanks - beyond the small detail i mailed about a few minutes ago > > the series looks good: i'll queue this up in tracing/blktrace unless > > Jens has second thoughts. > > > > Lets note that this approach still has the (long existing) > > limitation that only one device can be block-traced at a time. > > > > No, both userspace blktrace and ftrace-plugin trace can trace > more than one device at a time. > > # btrace /dev/sda /dev/dm-0 > > or > > # echo 1 > /sys/block/sda/trace/enable > # echo 1 > /sys/block/dm-0/trace/enable When they are independent - but not multiple partitions at a time: [root@aldebaran ~]# echo 1 > /sys/block/sda/sda1/trace/enable [root@aldebaran ~]# echo 1 > /sys/block/sda/sda2/trace/enable -bash: echo: write error: Device or resource busy [root@aldebaran ~]# Nor did i see any "trace all block IO in the system" kind of functionality in blktrace. (or maybe there's one that i missed?) > > Furthermore, various other aspects of act_log_check() itself > > could be expressed in terms of per tracepoint filters as well: > > the PID filter field for example - which is supported in the > > ioctl ABI but currently not exposed in the user-space blktrace > > utility. Same goes for the action mask which is frequently used. > > > > Actually action mask can be specified by 'blktrace -a/-A > mask/mask_name' Yes, this is what i meant by "which is frequently used". Ingo