From: Mingming cao <cmm@us.ibm.com>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
linux-kernel <linux-kernel@vger.kernel.org>,
lse-tech@lists.sourceforge.net
Subject: Re: [PATCH]Disk IO statistics for all disks
Date: Mon, 12 Nov 2001 16:02:30 -0800 [thread overview]
Message-ID: <3BF06316.46D48002@us.ibm.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0111121401070.7555-100000@penguin.transmeta.com>
Linus Torvalds wrote:
>
> On Mon, 12 Nov 2001, Mingming cao wrote:
> >
> > This is a patch to dynamically allocate the data buffers for the disk
> > statistics, and to extend the gathering of disk statistics to include
> > major numbers greater than 15.
>
> I would suggest instead just moving the statistics into the request queue,
> at which point it should be nicely per-controller already, and quite
> independent of major numbers etc.
>
> Oh, and it will be faster too, because you only need one lookup.
>
> Linus
I saw your suggestions related to this about a year ago. I like the
idea of doing statistics per-controller and getting rid of disk_index().
But by moving statistics into the request queue, under the current
implementation, we have to allocate statistics memory for every major,
since for every major there is a request_queue asscoiated with
it(blk_dev[MAX_BLKDEV]). Do you care about this?
--
Mingming Cao
IBM Linux Technology Center
503-578-5024 IBM T/L: 775-5024
cmm@us.ibm.com
http://www.ibm.com/linux/ltc
next parent reply other threads:[~2001-11-13 0:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.33.0111121401070.7555-100000@penguin.transmeta.com>
2001-11-13 0:02 ` Mingming cao [this message]
2001-11-14 2:18 ` [PATCH]Disk IO statistics for all disks (request queue) Mingming cao
2001-11-14 8:20 ` Marcel J.E. Mol
2001-11-14 14:59 ` M. Edward Borasky
2001-11-14 15:09 ` John Levon
2001-11-14 15:18 ` Marcel J.E. Mol
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=3BF06316.46D48002@us.ibm.com \
--to=cmm@us.ibm.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=lse-tech@lists.sourceforge.net \
--cc=torvalds@transmeta.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 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.