public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Alex Williamson <alex.williamson@hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [RFC] prefer allocations from nodes w/o CPUs
Date: Thu, 04 Nov 2004 17:22:04 +0000	[thread overview]
Message-ID: <1099588924.5561.4.camel@tdi> (raw)
In-Reply-To: <200411040857.25664.jbarnes@engr.sgi.com>

On Thu, 2004-11-04 at 09:16 -0800, Jesse Barnes wrote:
> On Thursday, November 4, 2004 9:11 am, Alex Williamson wrote:
> > On Thu, 2004-11-04 at 08:57 -0800, Jesse Barnes wrote:
> > > Small patch for the ia64 version of topology.h to make the zonelist
> > > building code prefer nodes w/o CPUs for allocations.  Do any platforms
> > > aside from Altix have nodes with only memory?  If not, then this will
> > > only affect sn2, otherwise I'm interested in hearing feedback.
> >
> >    Yes, hp sx1000 systems represent interleaved memory in a separate
> > node w/o cpus.
> 
> So does this patch make sense for those platforms too?  Or do we need 
> something fancier?  It'll make nodes w/o CPUs come before nodes with CPUs in 
> the zonelist (after the local node of course), even if the nodes with CPUs 
> are closer.

   That makes sense for us.  The interleaved memory should be somewhat
faster than truly remote memory.  Depending on the box configuration,
the interleaved memory node could be quite small and we'll run out
quickly, but better to make what use we can from it.  Thanks,

	Alex

-- 
Alex Williamson                             HP Linux & Open Source Lab


  parent reply	other threads:[~2004-11-04 17:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-04 16:57 [RFC] prefer allocations from nodes w/o CPUs Jesse Barnes
2004-11-04 17:11 ` Alex Williamson
2004-11-04 17:16 ` Jesse Barnes
2004-11-04 17:22 ` Alex Williamson [this message]
2004-11-04 17:32 ` Alex Tsariounov
2004-11-04 17:33 ` Jesse Barnes
2004-11-04 17:49 ` Jesse Barnes
2004-11-04 17:59 ` Alex Tsariounov

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=1099588924.5561.4.camel@tdi \
    --to=alex.williamson@hp.com \
    --cc=linux-ia64@vger.kernel.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