From: William Lee Irwin III <wli@holomorphy.com>
To: Erich Focht <efocht@ess.nec.de>
Cc: Andrew Morton <akpm@digeo.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
Michael Hohnbaum <hohnbaum@us.ibm.com>,
LSE <lse-tech@lists.sourceforge.net>
Subject: Re: per cpu time statistics
Date: Thu, 5 Dec 2002 03:14:43 -0800 [thread overview]
Message-ID: <20021205111443.GA18600@holomorphy.com> (raw)
In-Reply-To: <200212051157.29775.efocht@ess.nec.de>
On Thu, Dec 05, 2002 at 11:57:29AM +0100, Erich Focht wrote:
> My patch is basically the reverting patch plus changed ifdefs and a
> bunch of Kconfig entries. I'd be happy to get this feature back, no
> matter how it is implemented. I think it is necessary for performance
> analysis on HT, NUMA, SMT systems.
32-bit is not irrelevant, but there's certainly a 64-bit land where
the critical 32-bit correctness issue becomes a minor 64-bit
performance issue. This is the nature of extended 32-bit addressing.
By and large what is a severe and world-breaking correctness issue for
32-bit with extended addressing is a performance issue for the rest.
And so I feel we are all in harmony; the scheduler statistics are in
fact valuable on all platforms, it's just an question of basic "should
this overhead be required or optional?"
Bill
next prev parent reply other threads:[~2002-12-05 11:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-04 12:43 per cpu time statistics Erich Focht
2002-12-04 17:47 ` Andrew Morton
2002-12-04 18:30 ` William Lee Irwin III
2002-12-05 10:57 ` Erich Focht
2002-12-05 11:14 ` William Lee Irwin III [this message]
2002-12-05 17:01 ` Bill Davidsen
2002-12-06 17:31 ` Michael Hohnbaum
2002-12-06 17:55 ` [Lse-tech] " 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=20021205111443.GA18600@holomorphy.com \
--to=wli@holomorphy.com \
--cc=akpm@digeo.com \
--cc=efocht@ess.nec.de \
--cc=hohnbaum@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lse-tech@lists.sourceforge.net \
/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