From: compudj@krystal.dyndns.org (Mathieu Desnoyers)
Subject: [ltt-dev] liburcu cache line size
Date: Tue, 17 Aug 2010 14:51:22 -0400 [thread overview]
Message-ID: <20100817185122.GA4384@Krystal> (raw)
In-Reply-To: <4C6AD54F.4080006@polymtl.ca>
* David Goulet (david.goulet at polymtl.ca) wrote:
> Hi,
>
> I have some doubt about the value of #define CACHE_LINE_SIZE
> (urcu/arch_x86.h) that is set to 128.
>
> After some research and looking on my computer, the x86 architecture
> seems to have most of the time 64 bytes size. On my i7 920, here's what
> I have :
>
> # getconf LEVEL1_DCACHE_LINESIZE
> 64
>
> # cat /sys/devices/system/cpu/cpu0/cache/index0/coherency_line_size
> 64
>
> Since the Intel NetBurst microarch., the Intel manual says 64 bytes also
> and it has not changed apparently for Nehalem.
>
> So, Mathieu, why 128 bytes? UST is using that, if it's the wrong value
> here for x86, it could have an effect on cache pressure since 2 lines
> are required for structure less then 64 bytes.
See Linux kernel source:
arch/x86/Kconfig.cpu
#
# Define implied options from the CPU selection here
config X86_INTERNODE_CACHE_SHIFT
int
default "12" if X86_VSMP
default "7" if NUMA
default X86_L1_CACHE_SHIFT
and
config X86_L1_CACHE_SHIFT
int
default "7" if MPENTIUM4 || MPSC
default "6" if MK7 || MK8 || MPENTIUMM || MCORE2 || MATOM ||
MVIAC7 || X86_GENERIC || GENERIC_CPU
default "4" if X86_ELAN || M486 || M386 || MGEODEGX1
default "5" if MWINCHIP3D || MWINCHIPC6 || MCRUSOE || MEFFICEON
|| MCYRIXIII || MK6 || MPENTIUMIII || MPENTIUMII || M686 || M586MMX ||
M586TSC || M586 || MVIAC3_2 || MGEODE_LX
So Pentium 4 seems to have 128 bytes cache lines.
Hopefully the ScaleMP vSMP machine are rare enough (they would require a
4k alignment).
NUMA is not that rare, and requires 128 bytes cache lines too.
Can you send a patch for userspace RCU that documents this briefly in
urcu/arch_x86.h ? (just a summary of the info I pasted here would be
fine)
Thanks,
Mathieu
>
> Thanks!
> --
> David Goulet
> LTTng project, DORSAL Lab.
>
> PGP/GPG : 1024D/16BD8563
> BE3C 672B 9331 9796 291A 14C6 4AF7 C14B 16BD 8563
>
> _______________________________________________
> ltt-dev mailing list
> ltt-dev at lists.casi.polymtl.ca
> http://lists.casi.polymtl.ca/cgi-bin/mailman/listinfo/ltt-dev
>
--
Mathieu Desnoyers
Operating System Efficiency R&D Consultant
EfficiOS Inc.
http://www.efficios.com
next prev parent reply other threads:[~2010-08-17 18:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-17 18:30 David Goulet
2010-08-17 18:51 ` Mathieu Desnoyers [this message]
2010-08-17 19:06 ` David Goulet
2010-08-17 19:45 ` Mathieu Desnoyers
2010-08-17 19:54 ` Mathieu Desnoyers
2010-08-17 20:04 ` Alexandre Montplaisir
2010-08-17 20:27 ` Mathieu Desnoyers
2010-08-17 20:36 ` Alexandre Montplaisir
2010-08-17 20:53 ` Mathieu Desnoyers
2010-08-17 19:58 ` David Goulet
2010-08-17 20:24 ` Mathieu Desnoyers
2010-08-17 20:40 ` David Goulet
2010-08-17 20:51 ` Mathieu Desnoyers
2010-08-17 20:53 ` David Goulet
2010-08-17 20:55 ` Mathieu Desnoyers
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=20100817185122.GA4384@Krystal \
--to=compudj@krystal.dyndns.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox