From: Andrew Morton <akpm@digeo.com>
To: Lev Makhlis <mlev@despammed.com>
Cc: linux-kernel@vger.kernel.org, ricklind@us.ibm.com
Subject: Re: [PATCH] 2.5.46: overflow in disk stats
Date: Tue, 05 Nov 2002 22:06:38 -0800 [thread overview]
Message-ID: <3DC8B16E.EAFC854@digeo.com> (raw)
In-Reply-To: 200211060009.51684.mlev@despammed.com
Lev Makhlis wrote:
>
> Hi,
>
> I see that the SARD changes have been merged, but MSEC() still has
> the overflow problem. This takes care of it:
>
> --------------------------------------------------------------------------------------------------
>
> diff -urN linux-2.5.46.orig/drivers/block/genhd.c
> linux-2.5.46/drivers/block/genhd.c
> --- linux-2.5.46.orig/drivers/block/genhd.c Tue Nov 5 15:15:07 2002
> +++ linux-2.5.46/drivers/block/genhd.c Tue Nov 5 16:14:35 2002
> @@ -326,7 +326,13 @@
> }
> static inline unsigned MSEC(unsigned x)
> {
> - return x * 1000 / HZ;
> +#if 1000 % HZ == 0
> + return x * (1000 / HZ);
> +#elif HZ % 1000 == 0
> + return x / (HZ / 1000);
> +#else
> + return (x / HZ) * 1000 + (x % HZ) * 1000 / HZ;
> +#endif
> }
My brain just fell out. Why don't we just do
return (x / HZ) * 1000;
?
Yes, it'll return zero for the first second of disk activity.
I don't think that matters?
return ((x + HZ / 2) / HZ) * 1000;
would be more accurate too, and reduces it to half a second ;)
--- 25/drivers/block/genhd.c~msec-fix Tue Nov 5 21:59:35 2002
+++ 25-akpm/drivers/block/genhd.c Tue Nov 5 22:02:17 2002
@@ -324,10 +324,12 @@ static ssize_t disk_size_read(struct gen
{
return off ? 0 : sprintf(page, "%llu\n",(unsigned long long)get_capacity(disk));
}
-static inline unsigned MSEC(unsigned x)
+
+static unsigned jiffies_to_msec(unsigned jif)
{
- return x * 1000 / HZ;
+ return ((jif + HZ / 2) / HZ) * 1000;
}
+
static ssize_t disk_stat_read(struct gendisk * disk,
char *page, size_t count, loff_t off)
{
@@ -338,11 +340,11 @@ static ssize_t disk_stat_read(struct gen
"%8u %8u %8u"
"\n",
disk->reads, disk->read_merges, (u64)disk->read_sectors,
- MSEC(disk->read_ticks),
+ jiffies_to_msec(disk->read_ticks),
disk->writes, disk->write_merges, (u64)disk->write_sectors,
- MSEC(disk->write_ticks),
- disk->in_flight, MSEC(disk->io_ticks),
- MSEC(disk->time_in_queue));
+ jiffies_to_msec(disk->write_ticks),
+ disk->in_flight, jiffies_to_msec(disk->io_ticks),
+ jiffies_to_msec(disk->time_in_queue));
}
static struct disk_attribute disk_attr_dev = {
.attr = {.name = "dev", .mode = S_IRUGO },
_
next prev parent reply other threads:[~2002-11-06 6:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-06 5:09 [PATCH] 2.5.46: overflow in disk stats Lev Makhlis
2002-11-06 6:06 ` Andrew Morton [this message]
2002-11-06 6:20 ` Andrew Morton
2002-11-06 7:19 ` Rick Lindsley
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=3DC8B16E.EAFC854@digeo.com \
--to=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mlev@despammed.com \
--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