From: Anton Blanchard <anton@samba.org>
To: Shai Fultheim <shai@scalex86.org>
Cc: "'Andrew Morton'" <akpm@osdl.org>,
"'Linux Kernel ML'" <linux-kernel@vger.kernel.org>,
"'Jes Sorensen'" <jes@trained-monkey.org>,
mort@wildopensource.com
Subject: Re: [PATCH] PER_CPU [4/4] - PER_CPU-irq_stat
Date: Mon, 12 Jul 2004 10:02:19 +1000 [thread overview]
Message-ID: <20040712000218.GC30109@krispykreme> (raw)
In-Reply-To: <S264774AbUGIJyY/20040709095424Z+26@vger.kernel.org>
Hi,
> Please find below one out of collection of patched that move NR_CPU array
> variables to the per-cpu area. Please consider applying, any comment will
> highly appreciated.
...
> diff -Nru a/kernel/softirq.c b/kernel/softirq.c
> --- a/kernel/softirq.c 2004-07-09 01:34:13 -07:00
> +++ b/kernel/softirq.c 2004-07-09 01:34:13 -07:00
> @@ -36,8 +36,8 @@
> */
>
> #ifndef __ARCH_IRQ_STAT
> -irq_cpustat_t irq_stat[NR_CPUS] ____cacheline_aligned;
> -EXPORT_SYMBOL(irq_stat);
> +DEFINE_PER_CPU(irq_cpustat_t, irq_stat) ____cacheline_maxaligned_in_smp;
> +EXPORT_PER_CPU_SYMBOL(irq_stat);
> #endif
Is there a need for the cacheline alignment? We want to keep that per
cpu data area as packed as possible, we only want to explicitly pad if
we need to (eg other cpus are accessing that variable a lot).
Also it looks like we will have to push the above change into the other
architectures.
Anton
next prev parent reply other threads:[~2004-07-12 4:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-09 9:54 [PATCH] PER_CPU [4/4] - PER_CPU-irq_stat Shai Fultheim
2004-07-12 0:02 ` Anton Blanchard [this message]
2004-07-12 4:44 ` Shai Fultheim
[not found] ` <200407120444.i6C4iAws031156@fire-2.osdl.org>
2004-07-12 5:11 ` Andrew Morton
2004-07-12 5:19 ` Shai Fultheim
[not found] ` <20040712044410.46293162B72@lists.samba.org>
2004-07-12 8:57 ` Anton Blanchard
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=20040712000218.GC30109@krispykreme \
--to=anton@samba.org \
--cc=akpm@osdl.org \
--cc=jes@trained-monkey.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mort@wildopensource.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.