All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Peschke <mp3@de.ibm.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: linux-scsi@vger.kernel.org
Subject: Re: [Patch] SCSI statistics
Date: Tue, 19 Sep 2006 18:33:14 +0200	[thread overview]
Message-ID: <45101BCA.6090608@de.ibm.com> (raw)
In-Reply-To: <1158614913.3182.78.camel@laptopd505.fenrus.org>

Arjan van de Ven wrote:
> On Mon, 2006-09-18 at 13:20 +0200, Martin Peschke wrote:
>> This patch makes the SCSI mid layer report statistics data, i.e. request
>> sizes, request latencies, request results and queue utilisation.
>> For sample output please see below. This data is only gathered if these
>> statistics have been enabled by users at run time (default is off).
>>
>> It is crucial (for us) to be able to look at such kernel level data in
>> case of customer situations. It allows us to determine what kind of
>> requests might be involved in performance situations. This information
>> helps to understand whether one faces a device issue or a Linux issue.
>> Not being able to tap into performance data is regarded as a big minus
>> by some enterprise customers, who are reluctant to use Linux SCSI
>> support or Linux.
>>
>> Patch is against 2.6.18-rc6-mm2, as it requires the statistics
>> infrastructure patches.
> 
> 
> wouldn't this be nicer as a block level functionality?

I won't mind as long as the data closely resembles the actual
I/O traffic to and from devices.


      parent reply	other threads:[~2006-09-19 16:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-18 11:20 [Patch] SCSI statistics Martin Peschke
2006-09-18 21:28 ` Arjan van de Ven
2006-09-18 21:34   ` Matthew Wilcox
2006-09-19 16:48     ` Martin Peschke
2006-09-19 16:33   ` Martin Peschke [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=45101BCA.6090608@de.ibm.com \
    --to=mp3@de.ibm.com \
    --cc=arjan@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.