public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@digeo.com>
To: Rick Lindsley <ricklind@us.ibm.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC][PATCH] sard changes for 2.5.34
Date: Wed, 11 Sep 2002 19:42:26 -0700	[thread overview]
Message-ID: <3D7FFF12.24B0FDAA@digeo.com> (raw)
In-Reply-To: 200209120210.g8C2AkD26470@eng4.beaverton.ibm.com

Rick Lindsley wrote:
> 
> Here's a patch to put sard changes similar to those in 2.4 into 2.5.  I
> say "similar" because the I/O subsystem has changed sufficiently in 2.5
> that making them exactly the same might be more effort that it's
> worth.  Still, we do record per-partition reads/writes/sectors, and
> per-disk stats on the same plus queue time and number of I/O merges.
> Once applied, "cat /proc/diskstats" outputs this information.

It would be very nice to get better disk accounting into the kernel.

> Because in 2.5.34, gendisk->part[0] no longer is an hd_struct that
> refers to the whole disk, there wasn't a convenient place to record
> this information.  I gratuitously added an hd_struct to gendisk to have
> a place to store the information, below, but that's distasteful and
> ugly. I'd like to move it to a different place.
> 
> Also, with this patch, we are collecting stats twice, once for these
> stats and once for /proc/stat (kstat).  That's stupid and I'd like to
> get the stats only once and use them, perhaps, in two places.

kstat should be a lighter-weight per-cpu thing.  But the current
disk accounting in there would make it 12 kilobytes per CPU.

My vote: remove the disk accounting from kernel_stat and use this.
 
> What follows works, but needs refinements.  Comments welcome.

What are those refinements?

What userspace tools are available for interpreting this information?

  reply	other threads:[~2002-09-12  2:22 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-12  2:10 [RFC][PATCH] sard changes for 2.5.34 Rick Lindsley
2002-09-12  2:42 ` Andrew Morton [this message]
2002-09-12  2:50   ` Rik van Riel
2002-09-12  6:40   ` Rick Lindsley
2002-09-12  7:20     ` Andrew Morton
2002-09-12  9:18       ` Rick Lindsley
2002-09-12 10:01         ` Alexander Viro
2002-09-12 10:33           ` Rick Lindsley
2002-09-12 19:42         ` Andrew Morton
2002-09-12 20:38           ` Rik van Riel
2002-09-12 16:16       ` Rik van Riel
2002-09-12 16:48         ` Andrew Morton
2002-09-12 23:32       ` Denis Vlasenko
2002-09-12 18:49         ` Andrew Morton
2002-09-12 19:50           ` Rick Lindsley
  -- strict thread matches above, loose matches on Subject: below --
2002-09-13 11:39 Dipankar Sarma
2002-09-14 18:57 Lev Makhlis
2002-09-18 17:54 ` Randy.Dunlap
2002-09-18 19:43   ` Lev Makhlis

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=3D7FFF12.24B0FDAA@digeo.com \
    --to=akpm@digeo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ricklind@us.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