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

[Xen-devel] [PATCH 02/11] [XEN] exact node request


  • To: xen-devel@xxxxxxxxxxxxxxxxxxx
  • From: Dulloor <dulloor@xxxxxxxxx>
  • Date: Sun, 4 Apr 2010 15:30:14 -0400
  • Delivery-date: Sun, 04 Apr 2010 12:33:32 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=QGxn0rho2IZ7xH6+xAczNjlEWjEATg7d7yX8pFn+4P6OLmBcgJOujpy5qSdt2aMPjp /ncZLrs+k6qMwwDiqTLkiM7geUq/dQfeY0Ust/nHu0+yMAY/JXba+OGTPrqKbAWv4VkU lBsn0uQ5kxZT3u7W6wT9LmGpqzNKRarBwLuKU=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

Currently, xen might allocate memory from other nodes (if allocation
from requested node fails) even if the memflags specifies a node. For
initial memory allocation and certain other purposes, stricter
semantics are needed. The patch implements exact_node_request flag for
this.

-dulloor

Signed-off-by: Dulloor Rao <dulloor@xxxxxxxxxx>

Attachment: xen-02-exact-node-request.patch
Description: Text Data

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

 


Rackspace

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