public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: "Jörn Engel" <joern@logfs.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-scsi@vger.kernel.org
Subject: Re: [RFC][PATCH] Add a flight data recorder for scsi commands
Date: Tue, 27 Aug 2013 18:41:47 -0400	[thread overview]
Message-ID: <20130827224147.GD7293@logfs.org> (raw)
In-Reply-To: <20130827195422.0c23e47d@gandalf.local.home>

On Tue, 27 August 2013 19:54:22 -0400, Steven Rostedt wrote:
> On Tue, 27 Aug 2013 18:03:25 -0400
> Jörn Engel <joern@logfs.org> wrote:
> 
> > Here is a fun patch in an early state.  Essentially I want to trace
> > scsi commands, which has already been done long ago.  The problem I
> > have is that I care about all the scsi commands for one particular
> > device - without knowing in advance which device it will be.  Once I
> > know the device in question, I want to dump the last X commands.
> 
> Is the device passed to the trace point? If so, you can add a filter on
> that device. You can even create a separate buffer to just trace that
> device.

"without knowing in advance which device it will be"

I have to trace all devices, because I don't know the interesting one
ahead of time.  And after the fact, I only care about one device.  So
having per-device trace buffers seems to be The Right Approach(tm).

And having multiple trace buffers is where I cannot easily make my
problem fit your infrastructure.  

Jörn

--
If you're willing to restrict the flexibility of your approach,
you can almost always do something better.
-- John Carmack
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2013-08-28  0:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20130827220325.GB7293@logfs.org>
2013-08-27 22:17 ` [RFC][PATCH] Add a flight data recorder for scsi commands Jörn Engel
2013-08-28  5:09   ` Nicholas A. Bellinger
2013-08-28 14:28     ` Jörn Engel
2013-08-28 12:45   ` Bart Van Assche
2013-08-28 14:32     ` Jörn Engel
2013-08-27 23:54 ` Steven Rostedt
2013-08-27 22:41   ` Jörn Engel [this message]
2013-08-28  0:34     ` Steven Rostedt
2013-08-28 14:19       ` Jörn Engel

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=20130827224147.GD7293@logfs.org \
    --to=joern@logfs.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=rostedt@goodmis.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