From: James Bottomley <James.Bottomley@SteelEye.com>
To: Swen Schillig <swen@vnet.ibm.com>
Cc: Christof Schmitt <christof.schmitt@de.ibm.com>,
linux-scsi@vger.kernel.org,
Linux on 390 Port <LINUX-390@vm.marist.edu>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] zfcp: add some internal zfcp adapter statistics
Date: Sun, 25 Nov 2007 13:16:59 +0200 [thread overview]
Message-ID: <1195989419.3427.11.camel@localhost.localdomain> (raw)
In-Reply-To: <200710311133.52090.swen@vnet.ibm.com>
On Wed, 2007-10-31 at 11:33 +0100, Swen Schillig wrote:
> From: Swen Schillig <swen@vnet.ibm.com>
>
> add some statistics provided by the zFCP adapter to the sysfs
>
> The new zFCP adapter statistics provide a variety of information
> about the virtual adapter (subchannel). In order to collect this information
> the zFCP driver is extended on one side to query the adapter and
> on the other side summarize certain values which can then be fetched on demand.
> This information is made available via files(attributes) in the sysfs filesystem.
>
> The information provided by the new zFCP adapter statistics can be fetched
> by reading from the following files in the sysfs filesystem
>
> /sys/class/scsi_host/host<n>/seconds_active
> /sys/class/scsi_host/host<n>/requests
> /sys/class/scsi_host/host<n>/megabytes
> /sys/class/scsi_host/host<n>/utilization
This lot all look like they belong in the FC transport class statistics
(some even already exist there).
> These are the statistics on a virtual adapter (subchannel) level.
> In addition latency information is provided on a SCSI device level (LUN) which
> can be found at the following location
>
> /sys/class/scsi_device/<H:C:T:L>/device/cmd_latency
> /sys/class/scsi_device/<H:C:T:L>/device/read_latency
> /sys/class/scsi_device/<H:C:T:L>/device/write_latency
These look to duplicate to some degree the figures
in /sys/block/<dev>/stat. Isn't the block device the best place to
gather these, if they're useful? Since user latencies should probably
include elevator times.
James
next prev parent reply other threads:[~2007-11-25 11:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-31 10:33 Swen Schillig
2007-11-03 9:17 ` Heiko Carstens
2007-11-03 9:40 ` Heiko Carstens
2007-11-05 11:35 ` Swen Schillig
2007-11-05 15:12 ` Swen Schillig
2007-11-25 11:16 ` James Bottomley [this message]
2007-11-26 10:23 ` Swen Schillig
2007-12-06 9:40 ` 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=1195989419.3427.11.camel@localhost.localdomain \
--to=james.bottomley@steeleye.com \
--cc=LINUX-390@vm.marist.edu \
--cc=christof.schmitt@de.ibm.com \
--cc=linux-kernel@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
Powered by JetHome