From: Andreas Schwab <schwab@suse.de>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: "Zou, Nanhai" <nanhai.zou@intel.com>,
linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Reading /proc/stat is slooow
Date: Tue, 06 Dec 2005 17:10:40 +0000 [thread overview]
Message-ID: <jeslt6xib3.fsf@sykes.suse.de> (raw)
In-Reply-To: <20051206165800.GA6277@agluck-lia64.sc.intel.com> (Tony Luck's message of "Tue, 6 Dec 2005 08:58:00 -0800")
"Luck, Tony" <tony.luck@intel.com> writes:
> 2) The problem loop is already #ifdef'd out for PPC64 and ALPHA. We could add
> IA64 to that exclusive club and just not include the per irq sums. Since kstat_irqs()
> computes the sums in an "int", they will wrap frequently on a large system
> (512 cpus * default 250Hz = 128000 ... which wraps a 32-bit unsigned in 9 hours
> and 19 minutes) ... so their usefulness is questionable. Does xosview use
> the per-irq values?
It doesn't use them, it uses /proc/interrupts instead. So IMHO this would
be the preferred solution.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2005-12-06 17:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-02 17:42 Reading /proc/stat is slooow Andreas Schwab
2005-12-05 22:21 ` Luck, Tony
2005-12-05 23:36 ` Andreas Schwab
2005-12-05 23:46 ` Andreas Schwab
2005-12-06 0:19 ` Luck, Tony
2005-12-06 1:21 ` Luck, Tony
2005-12-06 6:15 ` Luck, Tony
2005-12-06 9:24 ` Zou, Nanhai
2005-12-06 16:58 ` Luck, Tony
2005-12-06 17:10 ` Andreas Schwab [this message]
2005-12-07 19:54 ` [PATCH] Drop per-irq counters from /proc/stat (Was: Reading /proc/stat is slooow) Luck, Tony
2005-12-06 9:57 ` Reading /proc/stat is slooow Andreas Schwab
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=jeslt6xib3.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nanhai.zou@intel.com \
--cc=tony.luck@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