This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] [PATCH 2/3] xend: Add multiple cpumasks support

To: Ryan Harper <ryanh@xxxxxxxxxx>, Ian Pratt <m+Ian.Pratt@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH 2/3] xend: Add multiple cpumasks support
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Tue, 15 Aug 2006 09:44:50 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 15 Aug 2006 01:45:11 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20060814184709.GP1694@xxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcbARxHFUEDLjiw6EduqSQAKle7CWA==
Thread-topic: [Xen-devel] [PATCH 2/3] xend: Add multiple cpumasks support
User-agent: Microsoft-Entourage/

On 14/8/06 7:47 pm, "Ryan Harper" <ryanh@xxxxxxxxxx> wrote:

> I didn't want the quotes either, nor the python list.  I guess I
> misinterpreted your suggestion for requirements.  As for the commas, it
> is certainly functional, but it sounds like we need some other cpumask
> field delimiter, any takers for "|" ?
> cpus = "0-3,^2|4-7|8|9-12"

This is more readable than comma-space delimiters. I mainly care that we
support Python list form in the config file though.

I think Ian's right that setting the same cpumask for all VCPUs ought to be
the most common operation: Xen ought to do something sensible with that (it
probably already does with the new scheduler). So fixing the *existing*
syntax to do the sensible domain-wide thing, if it doesn't already, would be

 -- Keir

Xen-devel mailing list