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>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	Jan Beulich <JBeulich@novell.com>
Subject: Re: [PATCH] libxc bitmap utils and vcpu-affinity
Date: Tue, 30 Mar 2010 17:27:54 +0100	[thread overview]
Message-ID: <C7D7E51A.F151%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <940bcfd21003300905y78754e2cu101055e429a303a1@mail.gmail.com>

On 30/03/2010 17:05, "Dulloor" <dulloor@gmail.com> wrote:

>> It actually bloats the libraries by a net 650 LOC
>> (747 added, 87 deleted according to diffstat).
> In the patch, we have used the library only for vcpu get/set affinity.
> There are clearly other opportunities (right now and in future) to use
> most of the functions provided by the library, which will offset this.
> Also, this provides a cleaner/standard way of using the cpumap
> structure in libxc.

Clearly it's not a simplicity win right now as it net adds a lot of code.
I'd rather see this as part of a patch series that actually uses it more
substantially. And even then I'd bet that half of this patch could be
removed as unused. If NUMA changes end up manipulating cpumaps in, say, a
dozen places then I could see this approach being useful, instead of
pointless abstraction (how it appears currently).

 -- Keir

      reply	other threads:[~2010-03-30 16:27 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
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 [this message]

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=C7D7E51A.F151%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).