From: Hannes Reinecke <hare@suse.de>
To: Narsimhulu Musini <nmusini@cisco.com>,
JBottomley@Parallels.com, linux-scsi@vger.kernel.org
Cc: Sesidhar Baddela <sebaddel@cisco.com>
Subject: Re: [PATCH 8/9] snic:Add event tracing to capture IO events.
Date: Mon, 02 Mar 2015 14:34:55 +0100 [thread overview]
Message-ID: <54F466FF.1050600@suse.de> (raw)
In-Reply-To: <1423586616-18177-9-git-send-email-nmusini@cisco.com>
On 02/10/2015 05:43 PM, Narsimhulu Musini wrote:
> snic_trc.h contains global trace structure definitions for snic driver
>
> snic_trc.c adds tracing functionality to capture various IO events.
> It maintains global trace buffer to maintain recent history of IO events.
> It helps to understand the sequence of events prior to particular IO event,
> or hung, panic, etc,.
>
> Signed-off-by: Narsimhulu Musini <nmusini@cisco.com>
> Signed-off-by: Sesidhar Baddela <sebaddel@cisco.com>
Hmm. There _is_ a tracing infrastructure in the kernel.
Any particular reason why you insist on creating your own?
Cheers,
Hannes
--
Dr. Hannes Reinecke zSeries & Storage
hare@suse.de +49 911 74053 688
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: F. Imendörffer, J. Smithard, J. Guild, D. Upmanyu, G. Norton
HRB 21284 (AG Nürnberg)
--
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:[~2015-03-02 13:34 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-10 16:43 [PATCH 0/9] snic:initial submission of snic driver for Cisco SCSI HBA Narsimhulu Musini
2015-02-10 16:43 ` [PATCH 1/9] snic: snic module infrastructure Narsimhulu Musini
2015-03-02 12:39 ` Hannes Reinecke
2015-03-11 8:33 ` Narsimhulu Musini (nmusini)
2015-02-10 16:43 ` [PATCH 2/9] snic:Add interrupt, resource firmware interfaces Narsimhulu Musini
2015-03-02 12:53 ` Hannes Reinecke
2015-03-11 8:35 ` Narsimhulu Musini (nmusini)
2015-02-10 16:43 ` [PATCH 3/9] snic:Add meta request, handling of meta requests Narsimhulu Musini
2015-03-02 12:56 ` Hannes Reinecke
2015-03-11 8:35 ` Narsimhulu Musini (nmusini)
2015-02-10 16:43 ` [PATCH 4/9] snic:Add snic target discovery Narsimhulu Musini
2015-03-02 12:59 ` Hannes Reinecke
2015-03-11 8:35 ` Narsimhulu Musini (nmusini)
2015-02-10 16:43 ` [PATCH 5/9] snic:add SCSI handling, AEN, and fwreset handling Narsimhulu Musini
2015-03-02 13:26 ` Hannes Reinecke
2015-03-11 8:39 ` Narsimhulu Musini (nmusini)
2015-02-10 16:43 ` [PATCH 6/9] snic:Add low level queuing interfaces Narsimhulu Musini
2015-03-02 13:32 ` Hannes Reinecke
2015-03-11 8:39 ` Narsimhulu Musini (nmusini)
2015-02-10 16:43 ` [PATCH 7/9] snic:Add sysfs entries to list stats and trace data Narsimhulu Musini
2015-03-02 13:33 ` Hannes Reinecke
2015-03-11 8:39 ` Narsimhulu Musini (nmusini)
2015-02-10 16:43 ` [PATCH 8/9] snic:Add event tracing to capture IO events Narsimhulu Musini
2015-03-02 13:34 ` Hannes Reinecke [this message]
2015-03-11 8:40 ` Narsimhulu Musini (nmusini)
2015-02-10 16:43 ` [PATCH 9/9] snic:Add Makefile, patch Kconfig, MAINTAINERS Narsimhulu Musini
2015-03-02 13:35 ` Hannes Reinecke
2015-03-11 8:40 ` Narsimhulu Musini (nmusini)
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=54F466FF.1050600@suse.de \
--to=hare@suse.de \
--cc=JBottomley@Parallels.com \
--cc=linux-scsi@vger.kernel.org \
--cc=nmusini@cisco.com \
--cc=sebaddel@cisco.com \
/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;
as well as URLs for NNTP newsgroup(s).