public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjan@infradead.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Nick Piggin <npiggin@suse.de>, Jan Beulich <JBeulich@novell.com>,
	tglx@linutronix.de, linux-kernel@vger.kernel.org, hpa@zytor.com,
	Ravikiran Thirumalai <kiran@scalex86.org>,
	Shai Fultheim <shai@scalemp.com>
Subject: Re: [PATCH] x86: eliminate redundant/contradicting cache line size config options
Date: Wed, 18 Nov 2009 20:52:40 -0800	[thread overview]
Message-ID: <20091118205240.11d3d660@infradead.org> (raw)
In-Reply-To: <20091119035640.GA18236@elte.hu>

On Thu, 19 Nov 2009 04:56:40 +0100
Ingo Molnar <mingo@elte.hu> wrote:

> 
> * Nick Piggin <npiggin@suse.de> wrote:
> 
> > The only other use for L1 cache size macro is to pack objects to 
> > cachelines better (so they always use the fewest number of lines).
> > But this case is more rare nowadays people don't really count
> > cachelines anymore, but I think even then it makes sense for it to
> > be the largest line size in the system because we don't know how
> > big L1s are, and if you want opimal L1 packing, you likely also
> > want optimal Ln packing.
> 
> We could do that - but then this default of X86_INTERNODE_CACHE_SHIFT:
> 
> +       default "7" if NUMA
> 
> will bite us and turns the 64 bytes L1_CACHE_BYTES into an effective
> 128 bytes value.
> 
> So ... are you arguing for an increase of the default x86 linesize to 
> 128 bytes?

128 is basically always wrong.
(unless you have a P4... but for default really we should not care
about those anymore)


-- 
Arjan van de Ven 	Intel Open Source Technology Centre
For development, discussion and tips for power savings, 
visit http://www.lesswatts.org

  reply	other threads:[~2009-11-19  4:51 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-13 11:54 [PATCH] x86: eliminate redundant/contradicting cache line size config options Jan Beulich
2009-11-16  4:14 ` Nick Piggin
2009-11-16  8:08   ` Jan Beulich
2009-11-16 10:56     ` Nick Piggin
2009-11-19  3:56       ` Ingo Molnar
2009-11-19  4:52         ` Arjan van de Ven [this message]
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=20091118205240.11d3d660@infradead.org \
    --to=arjan@infradead.org \
    --cc=JBeulich@novell.com \
    --cc=hpa@zytor.com \
    --cc=kiran@scalex86.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=npiggin@suse.de \
    --cc=shai@scalemp.com \
    --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