public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Jan Kara <jack@suse.cz>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] blktrace: Send BLK_TN_PROCESS events to all running traces
Date: Tue, 15 Oct 2013 09:17:47 -0600	[thread overview]
Message-ID: <20131015151747.GL541@kernel.dk> (raw)
In-Reply-To: <20131015094035.GA12416@quack.suse.cz>

On Tue, Oct 15 2013, Jan Kara wrote:
> On Mon 23-09-13 13:37:23, Jan Kara wrote:
> > On Tue 17-09-13 22:30:31, Jan Kara wrote:
> > > Currently each task sends BLK_TN_PROCESS event to the first traced
> > > device it interacts with after a new trace is started. When there are
> > > several traced devices and the task accesses more devices, this logic
> > > can result in BLK_TN_PROCESS being sent several times to some devices
> > > while it is never sent to other devices. Thus blkparse doesn't display
> > > command name when parsing some blktrace files.
> > > 
> > > Fix the problem by sending BLK_TN_PROCESS event to all traced devices
> > > when a task interacts with any of them.
> >   Jens, any opinion about this?
>   Jens, ping? I guess this patch fell through cracks...

Queued up for 3.13, thanks!

-- 
Jens Axboe


  parent reply	other threads:[~2013-10-15 15:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-17 20:30 [PATCH] blktrace: Send BLK_TN_PROCESS events to all running traces Jan Kara
2013-09-23 11:37 ` Jan Kara
2013-10-15  9:40   ` Jan Kara
2013-10-15 14:18     ` Jeff Moyer
2013-10-15 15:17     ` Jens Axboe [this message]
2013-09-23 13:02 ` 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=20131015151747.GL541@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=jack@suse.cz \
    --cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox