From: Larry McVoy <lm@bitmover.com>
To: "Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>
Cc: linux-kernel@vger.kernel.org, Linus Torvalds <torvalds@transmeta.com>
Subject: Re: lmbench results for 2.4 and 2.5 -- updated results
Date: Mon, 24 Mar 2003 12:01:05 -0800 [thread overview]
Message-ID: <20030324200105.GA5522@work.bitmover.com> (raw)
In-Reply-To: <C8C38546F90ABF408A5961FC01FDBF19010485F1@fmsmsx405.fm.intel.com>
On Mon, Mar 24, 2003 at 11:53:44AM -0800, Pallipadi, Venkatesh wrote:
> --- LMbench/src/lat_pagefault.c.org Mon Mar 24 10:40:46 2003
> +++ LMbench/src/lat_pagefault.c Mon Mar 24 10:54:34 2003
> @@ -67,5 +67,5 @@
> n++;
> }
> use_int(sum);
> - fprintf(stderr, "Pagefaults on %s: %d usecs\n", file, usecs/n);
> + fprintf(stderr, "Pagefaults on %s: %f usecs\n", file, (1.0 *
> usecs) / n);
> }
It's been a long time since I've looked at this benchmark, has anyone
stared at it and do you believe it measures anything useful? If not,
I'll drop it from a future release. If I remember correctly what I
was trying to do was to measure the cost of setting up the mapping
but I might be crackin smoke.
--
---
Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
next prev parent reply other threads:[~2003-03-24 19:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-24 19:53 lmbench results for 2.4 and 2.5 -- updated results Pallipadi, Venkatesh
2003-03-24 20:01 ` Larry McVoy [this message]
2003-03-24 21:09 ` Martin J. Bligh
2003-03-24 23:36 ` Andrew Morton
2003-03-24 22:04 ` Larry McVoy
2003-03-24 22:04 ` Martin J. Bligh
2003-03-24 22:23 ` Larry McVoy
2003-03-24 22:19 ` Chris Friesen
2003-03-25 18:23 ` Martin J. Bligh
2003-03-26 1:50 ` Larry McVoy
2003-03-26 2:09 ` Martin J. Bligh
-- strict thread matches above, loose matches on Subject: below --
2003-03-24 20:11 Nakajima, Jun
2003-03-22 16:11 lmbench results for 2.4 and 2.5 Chris Friesen
2003-03-24 6:08 ` lmbench results for 2.4 and 2.5 -- updated results Chris Friesen
2003-03-24 8:39 ` Linus Torvalds
2003-03-24 9:03 ` William Lee Irwin III
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=20030324200105.GA5522@work.bitmover.com \
--to=lm@bitmover.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
--cc=venkatesh.pallipadi@intel.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