From: Hagen Paul Pfeifer <hagen@jauu.net>
To: linux-kernel@vger.kernel.org
Cc: Ingo Molnar <mingo@elte.hu>, Hagen Paul Pfeifer <pfeifer@netlab.nec.de>
Subject: [PATCH] INTERNODE_CACHE_SHIFT redefinition for hot spot structures
Date: Wed, 30 May 2007 11:50:07 +0200 [thread overview]
Message-ID: <20070530095007.GA24087@c3po.0xdef.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 2539 bytes --]
I followed code in include/linux/mmzone.h and attract attention to the padding
construct for struct zone:
struct zone_padding {
char x[0];
} ____cacheline_internodealigned_in_smp;
The definition for ____cacheline_internodealigned_in_smp
is definded as __attribute__((__aligned__(1 << (INTERNODE_CACHE_SHIFT))))
INTERNODE_CACHE_SHIFT in turn is defined as L1_CACHE_SHIFT for all
architectures (expect x86_64) as L1_CACHE_SHIFT - which is not that what
everybody should expected if they use ____cacheline_internodealigned_in_smp!
The comment stated out: "The maximum alignment needed for some critical
structures. These could be inter-node cacheline sizes/L3 cacheline size etc.
Define this in asm/cache.h for your arch"
If a architecture redefine INTERNODE_CACHE_SHIFT (as x86_64) this patch has no
effects at all. All other architecture will profit from a better cache line
utilization.
The superior solution is to utilize the gcc 4.2 alternative to use the cpuid
instruction (which is new in gcc release 4.2) to gather CPU attributes at
compile time and replace the static
#define L1_CACHE_BYTES (1 << L1_CACHE_SHIFT)
macros for at least amd/intel processors- but that is another thought ...
(Which _user_ knows the l1/l2 cache line size of the current CPU if they are
different for different models (e.g P4)? If this fails -> fall back to standard
size). But as I said - this is a idea.
See gcc/config/i386/driver-i386.c:host_detect_local_cpu() for more information
in the gcc devel branch.
Salaam
Hagen Paul Pfeifer
Increase (double) the definition for INTERNODE_CACHE_SHIFT to accommodate a
higher cache line size for l2 and l3 cacheline sizes - compared to l1 cache
line size. The introduced overhead for architectures where the l1 cache line
size correspond to the l2 cache line size is evanescent small, cause
INTERNODE_CACHE_SHIFT is used only for hot spots.
Signed-off-by: Hagen Paul Pfeifer <hagen@jauu.net>
---
include/linux/cache.h | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
[-- Attachment #2: 46130e6afdad1c3df698bde8b86ab89568a3f6d9.diff --]
[-- Type: text/x-patch, Size: 416 bytes --]
diff --git a/include/linux/cache.h b/include/linux/cache.h
index 4552504..ebc366c 100644
--- a/include/linux/cache.h
+++ b/include/linux/cache.h
@@ -48,7 +48,7 @@
* size etc. Define this in asm/cache.h for your arch
*/
#ifndef INTERNODE_CACHE_SHIFT
-#define INTERNODE_CACHE_SHIFT L1_CACHE_SHIFT
+#define INTERNODE_CACHE_SHIFT (L1_CACHE_SHIFT + 1)
#endif
#if !defined(____cacheline_internodealigned_in_smp)
reply other threads:[~2007-05-30 9:50 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20070530095007.GA24087@c3po.0xdef.net \
--to=hagen@jauu.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=pfeifer@netlab.nec.de \
/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
all inboxes | Powered by JetHome®