From: "Jörn Engel" <joern@logfs.org>
To: Bart Van Assche <bvanassche@acm.org>
Cc: Steven Rostedt <rostedt@goodmis.org>, linux-scsi@vger.kernel.org
Subject: Re: [RFC][PATCH] Add a flight data recorder for scsi commands
Date: Wed, 28 Aug 2013 10:32:58 -0400 [thread overview]
Message-ID: <20130828143258.GD15917@logfs.org> (raw)
In-Reply-To: <521DF0DA.10004@acm.org>
On Wed, 28 August 2013 14:45:14 +0200, Bart Van Assche wrote:
>
> Isn't this facility something that overlaps with what Wireshark can
> already do today ? Wireshark can already capture SCSI traces for
> several transport types (iSCSI, USB, ...). For other transports,
> e.g. FC, I'd prefer to see Wireshark being extended instead of
> adding more SCSI tracing mechanisms in the SCSI core.
Wireshark would be great if there was a reproducable testcase and a
developer could sit down for an afternoon and collect some traces.
But how would you deal with rare cases that require around a year to
reproduce per device and only matter when dealing with many devices?
Jörn
--
Data expands to fill the space available for storage.
-- Parkinson's Law
--
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
next prev parent reply other threads:[~2013-08-28 16:06 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 [this message]
2013-08-27 23:54 ` Steven Rostedt
2013-08-27 22:41 ` Jörn Engel
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=20130828143258.GD15917@logfs.org \
--to=joern@logfs.org \
--cc=bvanassche@acm.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