mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tony.Young@ir.com
To: chris@scary.beasts.org
Cc: slug@slug.org.au, csa@oss.sgi.com, linux-kernel@vger.kernel.org
Subject: RE: Linux Disk Performance/File IO per process
Date: Mon, 29 Jan 2001 13:50:26 +1100	[thread overview]
Message-ID: <C0D2F5944500D411AD8A00104B31930E10809C@ir_nt_server2> (raw)



> -----Original Message-----
> From: Chris Evans [mailto:chris@scary.beasts.org]
> Sent: Monday, 29 January 2001 13:04
> To: Tony Young
> Cc: slug@slug.org.au; csa@oss.sgi.com; linux-kernel@vger.kernel.org
> Subject: Re: Linux Disk Performance/File IO per process
> 
> 
> 
> On Mon, 29 Jan 2001 Tony.Young@ir.com wrote:
> 
> > All,
> >
> > I work for a company that develops a systems and 
> performance management
> > product for Unix (as well as PC and TANDEM) called 
> PROGNOSIS. Currently we
> > support AIX, HP, Solaris, UnixWare, IRIX, and Linux.
> >
> > I've hit a bit of a wall trying to expand the data provided 
> by our Linux
> > solution - I can't seem to find anywhere that provides the 
> metrics needed to
> > calculate disk busy in the kernel! This is a major piece of 
> information that
> > any mission critical system administrator needs to 
> successfully monitor
> > their systems.
> 
> Stephen Tweedie has a rather funky i/o stats enhancement patch which
> should provide what you need. It comes with RedHat7.0 and gives decent
> disk statistics in /proc/partitions.
> 
> Unfortunately this patch is not yet in the 2.2 or 2.4 kernel. 
> I'd like to
> see it make the kernel as a 2.4.x item. Failing that, it'll 
> probably make
> the 2.5 kernel.
> 
> Cheers
> Chris
>

Thanks to both Jens and Chris - this provides the information I need to
obtain our busy rate
It's unfortunate that the kernel needs to be patched to provide this
information - hopefully it will become part of the kernel soon.

I had a response saying that this shouldn't become part of the kernel due to
the performance cost that obtaining such data will involve. I agree that a
cost is involved here, however I think it's up to the user to decide which
cost is more expensive to them - getting the data, or not being able to see
how busy their disks are. My feeling here is that this support could be user
configurable at run time - eg 'cat 1 > /proc/getdiskperf'.

Thanks for your quick responses.

Tony...
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

             reply	other threads:[~2001-01-29  2:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-29  2:50 Tony.Young [this message]
2001-01-29 13:26 ` Chris Evans
2001-01-29 22:41   ` List User
2001-01-30  2:18     ` James Sutherland
2001-01-30  2:49       ` List User
  -- strict thread matches above, loose matches on Subject: below --
2001-01-29  1:54 Tony.Young
2001-01-29  2:02 ` Jens Axboe
2001-01-29  2:04 ` Chris Evans
2001-01-29 15:39   ` Szabolcs Szakacsits
2001-01-29 18:27     ` Mike Galbraith

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=C0D2F5944500D411AD8A00104B31930E10809C@ir_nt_server2 \
    --to=tony.young@ir.com \
    --cc=chris@scary.beasts.org \
    --cc=csa@oss.sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=slug@slug.org.au \
    /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

all inboxes | Powered by JetHome®