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>
Subject: Re: [Xen-devel] [PATCH 2/3] xend: Add multiple cpumasks support
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Mon, 14 Aug 2006 18:55:23 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 14 Aug 2006 10:58:59 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20060814174812.GO1694@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: Aca/ytCPDzQ3ESu+EduTIwAKle7CWA==
Thread-topic: [Xen-devel] [PATCH 2/3] xend: Add multiple cpumasks support
User-agent: Microsoft-Entourage/

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

>> I'm not sure about the use of ', ' as a delimiter. It would be less
>> confusing to strictly require the use of the list form. I would imagine it's
>> then clearest used as:
>> Cpus = []
>> Cpus[0] = '2-5'
>> Cpus[1] = '3-4'
>> ...
> I'd prefer to not have to use any language arrays.  I'm not sure how
> this will map to the xml-based config files that Ewan was talking about,
> but I suppose he will have to come up with something since we have
> things like the disk parameter which is in python list format.

I think that'll be a different format again. Perhaps a separate cpu-info
section of the file for each VCPU, within which we specify the affinity
info. I'm pretty sure we won't go for a single string with whitespace

Anyhow, the current patch does have flexibility in its favour, since it
supports the list format *and* the string format. So I guess it's okay

 -- Keir

Xen-devel mailing list