public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthew Wilcox <matthew@wil.cx>
To: Swen Schillig <swen@vnet.ibm.com>
Cc: James Bottomley <James.Bottomley@steeleye.com>,
	linux-s390@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: [RFC] zfcp: add statistics and other zfcp related information to sysfs
Date: Mon, 3 Sep 2007 06:40:59 -0600	[thread overview]
Message-ID: <20070903124059.GP14130@parisc-linux.org> (raw)
In-Reply-To: <200709031416.21901.swen@vnet.ibm.com>

On Mon, Sep 03, 2007 at 02:16:21PM +0200, Swen Schillig wrote:
> /sys/bus/ccw/drivers/zfcp/0.0.1707 
> /* information for the virtual adapter */
> 	statistic_services/ 	
> 		requests	
> 		megabytes
> 		utilization
> 		seconds_active
> /* LUN specific info for channel- and fabric-latency */
> 	0x500507630300c562/0x401040a600000000/  
> 		read_latency
> 		write_latency
> 		cmd_latency
> 
> Please comment if this would be an acceptable way to publish 
> the additional information.

This seems like it might be information that other adapters could,
in theory, also provide.  Maybe the first set of stats should
be added to /sys/class/scsi_host/hostN/ and the second set to
/sys/class/scsi_device/H:C:T:L/ ?  The names of the individual files
make sense to me.

-- 
Intel are signing my paycheques ... these opinions are still mine
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours.  We can't possibly take such
a retrograde step."

  reply	other threads:[~2007-09-03 12:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-03 12:16 [RFC] zfcp: add statistics and other zfcp related information to sysfs Swen Schillig
2007-09-03 12:40 ` Matthew Wilcox [this message]
2007-09-05 10:33   ` Swen Schillig

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=20070903124059.GP14130@parisc-linux.org \
    --to=matthew@wil.cx \
    --cc=James.Bottomley@steeleye.com \
    --cc=linux-s390@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=swen@vnet.ibm.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