From: Andrew Morton <akpm@linux-foundation.org>
To: Ravikiran G Thirumalai <kiran@scalex86.org>
Cc: Andi Kleen <ak@suse.de>,
linux-kernel@vger.kernel.org,
"Shai Fultheim (Shai@scalex86.org)" <shai@scalex86.org>
Subject: Re: [patch] x86_64: Avoid too many remote cpu references due to /proc/stat
Date: Thu, 12 Jul 2007 19:13:17 -0700 [thread overview]
Message-ID: <20070712191317.41217c7a.akpm@linux-foundation.org> (raw)
In-Reply-To: <20070713000615.GA11942@localdomain>
On Thu, 12 Jul 2007 17:06:16 -0700 Ravikiran G Thirumalai <kiran@scalex86.org> wrote:
> Too many remote cpu references due to /proc/stat.
>
> On x86_64, with newer kernel versions, kstat_irqs is a bit of a problem.
> On every call to kstat_irqs, the process brings in per-cpu data from all
> online cpus. Doing this for NR_IRQS, which is now 256 + 32 * NR_CPUS
> results in (256+32*63) * 63 remote cpu references on a 64 cpu config.
> /proc/stat is parsed by common commands like top, who etc, causing
> lots of cacheline transfers
(256+32*63) * 63 = 143136
Do you have any actual numbers for how much this hurts?
> This statistic seems useless. Other 'big iron' arches disable this.
> Can we disable computing/reporting this statistic? This piece of
> statistic is not human readable on x86_64 anymore,
Did you consider using percpu_counters (or such) at interrupt-time?
(warning: percpu_counters aren't presently interrupt safe).
> If not, can we optimize computing this statistic so as to avoid
> too many remote references (patch to follow)
You other patch is a straightforward optimisation and should just be merged.
But afaict it will only provide a 2x speedup which I doubt is sufficient?
Another thought is: how many of the NR_IRQS counters are actually non-zero?
Because a pretty obvious optimisation would be to have a global
bitmap[NR_IRQS] and do
if (!bitmap[irq])
bitmap[irq] = 1;
at interrupt-time, then just print a "0" for the interrupts which have
never occurred within show_stats().
next prev parent reply other threads:[~2007-07-13 2:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-13 0:06 [patch] x86_64: Avoid too many remote cpu references due to /proc/stat Ravikiran G Thirumalai
2007-07-13 0:09 ` [patch] " Ravikiran G Thirumalai
2007-07-13 2:13 ` Andrew Morton [this message]
2007-07-13 6:50 ` [patch] x86_64: " Ravikiran G Thirumalai
2007-07-13 10:03 ` Christoph Hellwig
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=20070712191317.41217c7a.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=ak@suse.de \
--cc=kiran@scalex86.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shai@scalex86.org \
/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