Linux s390 Architecture development
 help / color / mirror / Atom feed
From: Swen Schillig <swen@vnet.ibm.com>
To: James Bottomley <James.Bottomley@hansenpartnership.com>
Cc: Christof Schmitt <christof.schmitt@de.ibm.com>,
	linux-scsi@vger.kernel.org, linux-s390@vger.kernel.org,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] zfcp: add some internal zfcp adapter statistics
Date: Thu, 6 Dec 2007 10:40:34 +0100	[thread overview]
Message-ID: <200712061040.35297.swen@vnet.ibm.com> (raw)
In-Reply-To: <200711261123.05253.swen@vnet.ibm.com>

On Monday 26 November 2007 11:23, Swen Schillig wrote:
> On Sunday 25 November 2007 12:16, James Bottomley wrote:
> > 
> > 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).
> 
> They might look alike but they are not the same. The values provided through the FC transport
> class always refer to the physical port whereas the new values here refer to a virtual adapter or subchannel.
> The attributes provided here are all new and not covered or displayed anywhere else !
> 
> > 
> > > 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.
> 
> Actually no, the latencies covered here are channel- and fabric-latencies grouped by scsi-devices
> and not device-, scsi- or block-latencies. In contrast to the stats provided by the block-layer structure,
> tape devices will be covered here as well .
> 
> > 
> > James
> > 
> > 
> > 
> 
> Cheers Swen
> 

James

were my answers, comments sufficient enough to apply my patch
or is there still something missing required ?

Thanks

Cheers Swen

      parent reply	other threads:[~2007-12-06  9:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200710311133.52090.swen@vnet.ibm.com>
     [not found] ` <20071103091722.GA7807@osiris.boeblingen.de.ibm.com>
2007-11-09 13:07   ` [PATCH UPDATE] zfcp: add some internal zfcp adapter statistics Swen Schillig
2007-11-21 13:40     ` Swen Schillig
     [not found] ` <1195989419.3427.11.camel@localhost.localdomain>
     [not found]   ` <200711261123.05253.swen@vnet.ibm.com>
2007-12-06  9:40     ` Swen Schillig [this message]

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=200712061040.35297.swen@vnet.ibm.com \
    --to=swen@vnet.ibm.com \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=christof.schmitt@de.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.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