From: Arjan van de Ven <arjan@infradead.org>
To: Nick Piggin <npiggin@suse.de>
Cc: Ingo Molnar <mingo@elte.hu>, 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: Thu, 19 Nov 2009 07:59:58 -0800 [thread overview]
Message-ID: <20091119075958.2cba15f8@infradead.org> (raw)
In-Reply-To: <20091119081307.GA20534@wotan.suse.de>
On Thu, 19 Nov 2009 09:13:07 +0100
Nick Piggin <npiggin@suse.de> wrote:
>
> My other point was just this, but I don't care too much. But it is
> worded pretty negatively. The key here is that increasing the value
> too large tends to only cost a very small amount of size (and no
> increase in cacheline foot print, only RAM).
128 has a pretty significant impact on TPC-C benchmarks.....
it was the top issue until mainline fixed it to default to 64
next prev parent reply other threads:[~2009-11-19 15:58 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
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 [this message]
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=20091119075958.2cba15f8@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