From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Jackson Subject: Re: [PATCH 1 of 3 v5/leftover] libxl: enable automatic placement of guests on NUMA nodes [and 1 more messages] Date: Wed, 18 Jul 2012 11:44:42 +0100 Message-ID: <20486.37786.955556.785051@mariner.uk.xensource.com> References: <0411b2cebd725b193465.1341932614@Solace> <20485.35590.105351.434937@mariner.uk.xensource.com> <5fa66c8b9093399e5bc3.1342458792@Solace> <20485.43293.833036.352186@mariner.uk.xensource.com> <1342556600.18848.10.camel@dagon.hellion.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1342556600.18848.10.camel@dagon.hellion.org.uk> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Ian Campbell Cc: Andre Przywara , Stefano Stabellini , George Dunlap , Juergen Gross , xen-devel , Dario Faggioli List-Id: xen-devel@lists.xenproject.org Ian Campbell writes ("Re: [PATCH 1 of 3 v5/leftover] libxl: enable automatic placement of guests on NUMA nodes [and 1 more messages]"): > The 4.2 freeze is starting to drag on and reworking this significantly > at this stage seems likely to take quite a while Yes. > -- can we perhaps go > with the existing patches (with the known scalability limitation and > workaround of setting the explicit cpu affinity documented in the > release notes) and revisit for 4.3 and/or 4.2.1? I think the existing behaviour of these patches is unreleasable. In a couple of years' time people will try to run Xen 4.2 on larger machines and the result will be a hang (perhaps of their entire management stack) when they try to create a large guest. At the very least it should have a safety catch so that it disables itself, or something. Ian.