xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Keir Fraser <keir.fraser@eu.citrix.com>
To: Dulloor <dulloor@gmail.com>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH] libxc bitmap utils and vcpu-affinity
Date: Mon, 22 Mar 2010 07:30:13 +0000	[thread overview]
Message-ID: <C7CCCD05.D728%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <940bcfd21003212033t3c3bf074h663337b56dd5954e@mail.gmail.com>

On 22/03/2010 03:33, "Dulloor" <dulloor@gmail.com> wrote:

> This patch adds :
> 
> * A byte-based cpumask type(xenctl_cpumask) for setting vcpu-affinity
> as well as numa-node-affinity, etc in libxc.
> 
> * Add common bitmap utils to libxc, which can be used both for
> xenctl_cpumask (and with small changes for xenctl_cpumap, if desired),
> so that we can do common operations on cpumask easily.
> 
> As opposed to xenctl_cpumap, xenctl_cpumask is a static structure
> (just 4 bytes larger for 128 cpus), but keeps the interface/code
> cleaner. The domctl_interface version keeps the size of xenctl_cpumask
> consistent between xen and xen-tools.

I'm missing the motivation for this. It sounds less good than what we have
already.

 -- Keir

  reply	other threads:[~2010-03-22  7:30 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-22  3:33 [PATCH] libxc bitmap utils and vcpu-affinity Dulloor
2010-03-22  7:30 ` Keir Fraser [this message]
2010-03-22 17:44   ` Dulloor
2010-03-23 10:10     ` Jan Beulich
2010-03-23 11:05       ` Keir Fraser
2010-03-23 16:40         ` Dulloor
2010-03-23 16:41           ` Dulloor
2010-03-23 16:55             ` Dulloor
2010-03-30 14:42               ` Fwd: " Dulloor
2010-03-30 15:16                 ` Keir Fraser
2010-03-30 16:05                   ` Dulloor
2010-03-30 16:27                     ` Keir Fraser

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=C7CCCD05.D728%keir.fraser@eu.citrix.com \
    --to=keir.fraser@eu.citrix.com \
    --cc=dulloor@gmail.com \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).