All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ryan Harper <ryanh@us.ibm.com>
To: xen-devel@lists.xensource.com
Cc: Ryan Grimm <grimm@us.ibm.com>, Andi Kleen <ak@suse.de>
Subject: Re: Re: [PATCH 1/6][RESEND] xen: Add NUMA support to Xen
Date: Fri, 2 Jun 2006 10:55:29 -0500	[thread overview]
Message-ID: <20060602155529.GO1694@us.ibm.com> (raw)
In-Reply-To: <20060531180629.GH1694@us.ibm.com>

* Ryan Harper <ryanh@us.ibm.com> [2006-05-31 13:06]:
> * Ryan Harper <ryanh@us.ibm.com> [2006-05-24 14:02]:
> > * Andi Kleen <ak@suse.de> [2006-05-22 06:02]:
> > > 
> > > > The patch is function on 32-bit and 64-bit boxes and parse the SRAT
> > > > table and fills out the node_data array.  I installed a simple
> > > > keyhandler 'u' to dump the info to check that it was function after
> > > > booting up.
> > > 
> > > It mostly looks reasonable. As Keir noted you seem to have a lot of unnecessary
> > > changes (printk->DPRINTK, white space etc.)
> > 
> > Cleaned up.
> > 
> > > 
> > > I would also suggest you keep the numa emulation. It's useful for debugging
> > > so that developers without numa machines can reproduce numa issues.
> > 
> > Added numa emulation back in.  I've set it up such that if we fail to
> > find a numa-node we fallback on to emulation of one node.  This allows
> > the allocator code to not be filled with CONFIG_NUMA ifdefs as Keir
> > wanted. 
> 
> This last patch didn't have a functional cpu_to_node/node_to_cpumask.
> This patch fixes that up in addition to the previous cleanups.  Please
> take a look.

I wanted to follow up and see if anyone has had a chance to look at the
latest rework (patch 1 and 2).  Wasn't sure if this had fallen off your
radar.


-- 
Ryan Harper
Software Engineer; Linux Technology Center
IBM Corp., Austin, Tx
(512) 838-9253   T/L: 678-9253
ryanh@us.ibm.com

  reply	other threads:[~2006-06-02 15:55 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-01 21:56 [PATCH 1/6] xen: Add NUMA support to Xen Ryan Harper
2006-05-02 14:15 ` Keir Fraser
2006-05-02 14:39   ` Ryan Harper
2006-05-12 15:12   ` [PATCH 1/6][RESEND] " Ryan Harper
2006-05-13  9:07     ` Keir Fraser
2006-05-15 16:27       ` Andi Kleen
2006-05-15 16:54         ` Keir Fraser
2006-05-15 17:11           ` Ryan Harper
2006-05-15 17:17             ` Keir Fraser
2006-05-15 17:23               ` Keir Fraser
2006-05-15 17:25               ` Andi Kleen
2006-05-15 17:27               ` Ryan Harper
2006-05-15 17:34                 ` Keir Fraser
2006-05-15 20:32                   ` Ryan Harper
2006-05-15 20:46                     ` Andi Kleen
2006-05-16  7:49                       ` Keir Fraser
2006-05-16 12:57                         ` Andi Kleen
2006-05-16 13:03                           ` Keir Fraser
2006-05-19 21:08                             ` Ryan Harper
2006-05-20  8:50                               ` Keir Fraser
2006-05-22 11:01                               ` Andi Kleen
2006-05-24 19:02                                 ` Ryan Harper
2006-05-31 18:06                                   ` Ryan Harper
2006-06-02 15:55                                     ` Ryan Harper [this message]
2006-05-17 17:21                         ` Ryan Harper
2006-05-17 18:07                           ` Andi Kleen
2006-05-18 15:30                             ` Ryan Harper

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=20060602155529.GO1694@us.ibm.com \
    --to=ryanh@us.ibm.com \
    --cc=ak@suse.de \
    --cc=grimm@us.ibm.com \
    --cc=xen-devel@lists.xensource.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.