[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20120521090638.GE31407@gmail.com>
Date: Mon, 21 May 2012 11:06:38 +0200
From: Ingo Molnar <mingo@...nel.org>
To: Vlad Zolotarov <vlad@...lemp.com>
Cc: Thomas Gleixner <tglx@...utronix.de>,
linux-kernel <linux-kernel@...r.kernel.org>,
Ingo Molnar <mingo@...hat.com>,
"H. Peter Anvin" <hpa@...or.com>,
"Shai Fultheim (Shai@...leMP.com)" <Shai@...lemp.com>,
Ido Yariv <ido@...ery.com>
Subject: Re: [PATCH v3 0/2] Move x86_cpu_to_apicid to the __read_mostly
section
* Vlad Zolotarov <vlad@...lemp.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.
Mind explaining why it helps performance? Are these percpu
variables also accessed from other CPUs, increasing the cost of
false sharing of cache-lines?
Or is the problem that the 'cache line' size is 4096 bytes on
vSMP, making even singular cache misses expensive and you'd like
to move these next to each other?
So it would be nice to see some before/after PMU stats
demonstrating the improvement. (perf works on vSMP, right?)
Thanks,
Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists