[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] numa=on broken

  • To: Ryan Harper <ryanh@xxxxxxxxxx>
  • From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
  • Date: Fri, 30 Mar 2007 20:05:04 +0100
  • Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Fri, 30 Mar 2007 20:09:11 +0100
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: Acdy/lLQkZZxfN7xEdusYQAWy6hiGQ==
  • Thread-topic: [Xen-devel] numa=on broken

On 30/3/07 19:55, "Ryan Harper" <ryanh@xxxxxxxxxx> wrote:

>> This is just a simple exercise in code shuffling. :-)
> Giving that try right now, let you know in a fewl.
> I would have rather had the folks who changed the code actually test
> with numa=on.
> What are you thoughts about turning numa on by default or at least
> getting a numa=on run on a two-socket opteron in the xen-rt regressions.

Turning on by default is pointless because guests are not restricted to
running on specific nodes by default. Since manual intervention is required
to achieve that (right now at least) requiring numa=on is not much of a

Integration with xenrt is perhaps possible but we are constrained by machine
resources. Numa=on has been broken for over a month and noone else had yet
complained so it doesn't seem to be a priority for many people.

 -- Keir

Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.