From: "Jan Beulich" <JBeulich@novell.com>
To: "Nick Piggin" <npiggin@suse.de>
Cc: <mingo@elte.hu>, <tglx@linutronix.de>,
<linux-kernel@vger.kernel.org>, <hpa@zytor.com>
Subject: Re: [PATCH] x86: eliminate redundant/contradicting cache line size config options
Date: Mon, 16 Nov 2009 08:08:07 +0000 [thread overview]
Message-ID: <4B011677020000780001FD9D@vpn.id2.novell.com> (raw)
In-Reply-To: <20091116041407.GB5818@wotan.suse.de>
>>> Nick Piggin <npiggin@suse.de> 16.11.09 05:14 >>>
>On Fri, Nov 13, 2009 at 11:54:40AM +0000, Jan Beulich wrote:
>> Rather than having X86_L1_CACHE_BYTES and X86_L1_CACHE_SHIFT (with
>> inconsistent defaults), just having the latter suffices as the former
>> can be easily calculated from it.
>>
>> To be consistent, also change X86_INTERNODE_CACHE_BYTES to
>> X86_INTERNODE_CACHE_SHIFT, and set it to 7 (128 bytes) for NUMA to
>> account for last level cache line size (which here matters more than
>> L1 cache line size).
>
>I think if we're going to set it to 7 (128B, for Pentium 4), then
>we should set the L1 cache shift as well? Most alignments to
>prevent cacheline pingpong use L1 cache shift for this anyway?
But for P4 L1_CACHE_SHIFT already is 7.
>The internode thing is really just a not quite well defined thing
>because internode cachelines are really expensive and really big
>on vsmp so they warrant trading off extra space on some critical
>structures to reduce pingpong (but this is not to say that other
>structures that are *not* internode annotated do *not* need to
>worry about pingpong).
The internode one, as said in the patch description, should consider
the last level cache line size rather than L1, which 128 seems to be
a much better fit (without in introducing model dependencies like
for L1) than just using the L1 value directly.
Jan
next prev parent reply other threads:[~2009-11-16 8:08 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-13 11:54 Jan Beulich
2009-11-16 4:14 ` Nick Piggin
2009-11-16 8:08 ` Jan Beulich [this message]
2009-11-16 10:56 ` Nick Piggin
2009-11-19 3:56 ` Ingo Molnar
2009-11-19 4:52 ` Arjan van de Ven
2009-11-19 8:13 ` Nick Piggin
2009-11-19 8:38 ` Jan Beulich
2009-11-19 10:00 ` Nick Piggin
2009-11-19 15:59 ` Arjan van de Ven
2009-11-19 16:18 ` Nick Piggin
2009-11-19 17:53 ` Andi Kleen
2009-11-23 8:34 ` Ingo Molnar
2009-11-23 9:35 ` Nick Piggin
2009-11-23 10:09 ` Ingo Molnar
2009-11-23 14:52 ` Arjan van de Ven
2009-11-23 15:15 ` Nick Piggin
2009-11-19 4:42 ` [tip:x86/mm] x86: Eliminate " tip-bot for Jan Beulich
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=4B011677020000780001FD9D@vpn.id2.novell.com \
--to=jbeulich@novell.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=npiggin@suse.de \
--cc=tglx@linutronix.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®