linux-kernel - RE: [PATCH 0/2] Add percpu smp cacheline align section

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 7 May 2007 11:13:51 -0700
From:	"Yu, Fenghua" <fenghua.yu@...el.com>
To:	"Siddha, Suresh B" <suresh.b.siddha@...el.com>,
	"Christoph Lameter" <clameter@....com>
CC:	<akpm@...ux-foundation.org>, <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH 0/2] Add percpu smp cacheline align section

On Mon, May 07, 2007 at 10:30:16AM -0700, Christoph Lameter wrote:
> Call this area "cpu shared" or so?

There are some fields in percpu section which are accessed by other
cpu's but not cache line aligned, e.g. cpu_idle_state, flush_state in
x86-64. We don't want to place those fields into same subsection as
cacheline aligned fields.

So perhaps, I can change the section name
.data.percpu.cacheline_aligned_in_smp to
.data.percpu.shared_cacheline_aligned. And change macro
DEFINE_PER_CPU_CACHELINE_ALIGNED_IN_SMP to
DEFINE_PER_CPU_SHARED_CACHELINE_ALIGNED.

.data.percpu.shared_cacheline_aligned contains only cpu shared percpu
fields which are cacheline aligned. In future (or in a separate patch
series), we can define another percpu section .data.percpu.shared and
its macro DEFINE_PER_CPU_SHARED_CACHELINE_ALIGNED which store all of cpu
shared percpu fields. The new .data.percpu.shared and
DEFINE_PER_CPU_SHARED_CACHELINE_ALIGNED are for better coding and
understanding.

Thanks.

-Fenghua
-
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/