linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Brent Casavant <bcasavan@sgi.com>
To: Anton Blanchard <anton@samba.org>
Cc: "Jose R. Santos" <jrsantos@austin.ibm.com>,
	Andi Kleen <ak@suse.de>,
	"Martin J. Bligh" <Martin.Bligh@us.ibm.com>,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	linux-ia64@vger.kernel.org
Subject: Re: [PATCH 0/3] NUMA boot hash allocation interleaving
Date: Tue, 21 Dec 2004 10:23:59 -0600	[thread overview]
Message-ID: <Pine.SGI.4.61.0412211019150.48124@kzerza.americas.sgi.com> (raw)
In-Reply-To: <20041221114605.GB21710@krispykreme.ozlabs.ibm.com>

On Tue, 21 Dec 2004, Anton Blanchard wrote:

> > The difference between the two runs was with in noise of the benchmark on
> > my small setup.  I wont be able to get a larger NUMA system until next year,
> > so I'll retest when that happens.  In the mean time, I don't see a reason
> > either to stall this patch, but that may change on I get numbers on a
> > larger system.
> 
> Thanks Jose!
> 
> Brent, looks like we are happy on the ppc64 front.

I didn't realize this was ppc64 testing.  What was the exact setup
for the testing?  The patch as posted (and I hope clearly explained)
only turns on the behavior by default when both CONFIG_NUMA and
CONFIG_IA64 were active.  It could be activated on non-IA64 by setting
hashdist=1 on the boot line, or by modifying the patch.

I would hate to find out that the testing didn't actually enable the
new behavior.

Thanks,
Brent

-- 
Brent Casavant                          If you had nothing to fear,
bcasavan@sgi.com                        how then could you be brave?
Silicon Graphics, Inc.                    -- Queen Dama, Source Wars
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>

  reply	other threads:[~2004-12-21 16:23 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-14 17:53 Brent Casavant
2004-12-14 18:59 ` Martin J. Bligh
2004-12-14 19:13   ` Andi Kleen
2004-12-14 19:48     ` Brent Casavant
2004-12-14 20:08     ` Martin J. Bligh
2004-12-14 23:24       ` Brent Casavant
2004-12-14 22:00         ` Martin J. Bligh
2004-12-15  4:58           ` Andi Kleen
2004-12-15 14:47             ` Anton Blanchard
2004-12-15 23:37               ` Brent Casavant
2004-12-16  5:02               ` Andi Kleen
2004-12-16  5:13                 ` Anton Blanchard
2004-12-16 14:18                   ` Jose R. Santos
2004-12-20 16:56                     ` Jose R. Santos
2004-12-21 11:46                       ` Anton Blanchard
2004-12-21 16:23                         ` Brent Casavant [this message]
2004-12-23  2:19                           ` Jose R. Santos
2004-12-15  4:08         ` Andi Kleen
2004-12-15  7:14           ` Martin J. Bligh
2004-12-15  7:17             ` Andi Kleen
2004-12-15 15:08               ` Martin J. Bligh
2004-12-15 18:24               ` Brent Casavant
2004-12-15  7:41           ` Eric Dumazet
2004-12-15  7:46             ` Andi Kleen
2004-12-15  9:14               ` Andi Kleen
2004-12-14 23:24     ` Nick Piggin
2004-12-14 19:30   ` Brent Casavant
2004-12-14 20:10     ` Martin J. Bligh
2004-12-14 18:32 Luck, Tony
2004-12-15  0:28 ` Hiroyuki KAMEZAWA
2004-12-15 17:25 Luck, Tony

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=Pine.SGI.4.61.0412211019150.48124@kzerza.americas.sgi.com \
    --to=bcasavan@sgi.com \
    --cc=Martin.Bligh@us.ibm.com \
    --cc=ak@suse.de \
    --cc=anton@samba.org \
    --cc=jrsantos@austin.ibm.com \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.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