From: Keir Fraser <keir.fraser@eu.citrix.com>
To: Jan Beulich <JBeulich@novell.com>, Dulloor <dulloor@gmail.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH] libxc bitmap utils and vcpu-affinity
Date: Tue, 23 Mar 2010 11:05:27 +0000 [thread overview]
Message-ID: <C7CE50F7.E2C9%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <4BA8A1BC0200007800036662@vpn.id2.novell.com>
On 23/03/2010 10:10, "Jan Beulich" <JBeulich@novell.com> wrote:
>>>> Dulloor <dulloor@gmail.com> 22.03.10 18:44 >>>
>> Motivation for using xenctl_cpumask in Xen interfaces :
>> - xenctl_cpumap is just 4 bytes smaller than static xenctl_cpumask for
>> 128 cpus (128 would be good for quite some time). However, the new
>
> I don't buy this (we're already building for 256 CPUs, looking forward
> to further bump this in the not too distant future), and I'm generally
> opposed to introducing hard coded limits in a public interface.
We should use xenctl_cpumask everywhere for specifying physical CPU bitmaps,
even into guest NUMA interfaces if appropriate. I don't really care if it is
a bit harder to use than a static bitmap.
-- Keir
next prev parent reply other threads:[~2010-03-23 11:05 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
2010-03-22 17:44 ` Dulloor
2010-03-23 10:10 ` Jan Beulich
2010-03-23 11:05 ` Keir Fraser [this message]
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=C7CE50F7.E2C9%keir.fraser@eu.citrix.com \
--to=keir.fraser@eu.citrix.com \
--cc=JBeulich@novell.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).