From: Ingo Molnar <mingo@kernel.org>
To: Vlad Zolotarov <vlad@scalemp.com>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>,
linux-kernel <linux-kernel@vger.kernel.org>,
Shai@scalemp.com, ido@wizery.com
Subject: Re: [PATCH v4 0/2] Move x86_cpu_to_apicid to the __read_mostly section
Date: Mon, 21 May 2012 17:23:48 +0200 [thread overview]
Message-ID: <20120521152345.GC7068@gmail.com> (raw)
In-Reply-To: <1744141.b5asW8k6jC@vlad>
* Vlad Zolotarov <vlad@scalemp.com> wrote:
> Pls., consider applying this patch series.
> It contains the following changes:
> - Adds two new macros DEFINE_EARLY_PER_CPU_READ_MOSTLY() and
> DECLARE_EARLY_PER_CPU_READ_MOSTLY().
> - Adds "read-mostly" qualifier to the following variables in smp.h:
> - cpu_sibling_map
> - cpu_core_map
> - cpu_llc_shared_map
> - cpu_llc_id
> - cpu_number
> - x86_cpu_to_apicid
> - x86_bios_cpu_apicid
> - x86_cpu_to_logical_apicid
>
> As long as all the variables above are only written during the
> initialization, this change is meant to prevent the false
> sharing and improve the performance on large multiprocessor
> systems.
Why have you resent this? The feedback I gave has not been
addressed:
> Well, a quick tally of percpu variables on a 'make defconfig'
> kernel would tell us one way or another?
>
> Here there's almost 200 percpu variables active in the 64-bit
> x86 defconfig, and a quick random sample suggests that most
> are read-mostly.
>
> I have no fundamental prefer to either approach, but the
> direction taken should be justified explicitly, with numbers,
> arguments, etc. - also a short blurb somewhere in the headers
> that explains when they should be used, so that others can be
> aware of vSMP's special needs here.
Thanks,
Ingo
next prev parent reply other threads:[~2012-05-21 15:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-21 15:02 [PATCH v4 0/2] Move x86_cpu_to_apicid to the __read_mostly section Vlad Zolotarov
2012-05-21 15:23 ` Ingo Molnar [this message]
2012-05-21 15:42 ` Vlad Zolotarov
2012-05-21 20:19 ` Ingo Molnar
2012-05-22 15:55 ` Vlad Zolotarov
2012-05-22 15:59 ` Vlad Zolotarov
2012-05-23 9:16 ` Vlad Zolotarov
2012-06-07 8:18 ` Vlad Zolotarov
2012-06-11 9:00 ` Ingo Molnar
2012-06-11 9:08 ` Vlad Zolotarov
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=20120521152345.GC7068@gmail.com \
--to=mingo@kernel.org \
--cc=Shai@scalemp.com \
--cc=hpa@zytor.com \
--cc=ido@wizery.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=vlad@scalemp.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 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.