All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ryan Harper <ryanh@us.ibm.com>
To: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>
Cc: Ryan Grimm <grimm@us.ibm.com>, Ryan Harper <ryanh@us.ibm.com>,
	xen-devel@lists.xensource.com
Subject: Re: [PATCH 2/3] xend: Add multiple cpumasks support
Date: Mon, 14 Aug 2006 17:46:05 -0500	[thread overview]
Message-ID: <20060814224605.GT1694@us.ibm.com> (raw)
In-Reply-To: <A95E2296287EAD4EB592B5DEEFCE0E9D5723CC@liverpoolst.ad.cl.cam.ac.uk>

* Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk> [2006-08-14 17:41]:
> > > Either Keir's cpu[X] = "Y" approach or my cpu = [ "A","B","C" ]
> approach
> > > seem workable.
> > 
> > Your last email seemed to indicate to me that you didn't like using
> > quoted values in a list to separate per-vcpu cpumask values.  Maybe I
> > was mistaken.
> 
> If it's an honest python list I have no problem. Your example appeared
> to be some quoting within a string.

OK.

> My approach is a list too...
> 
> > > BTW: does the right thing happen in the face of vcpu hot plugging?
> i.e.
> > > if I unplug a vcpu and put it back in do I keep the old mask? If I
> add
> > > vcpus what mask do they get?
> > 
> > unplug events only affect a vcpu's status.  The internal struct
> > vcpu in the hypervisor is not de-allocated/re-allocated during hotplug
> > events.
> > 
> > We don't currently support a hotadd for vcpus that weren't allocated
> at
> > domain creation time.  The current method for simulating hot-add would
> > be to start a domain with 32 VCPUS and disable all by the number of
> > vcpus you currently want.  Ryan Grimm posted a patch back in February
> > that had xend do this by adding a new config option, max_vcpus, which
> > was used when calling xc_domain_max_vcpus() having the hypervisor
> alloc
> > that max number of vcpus and then using the vcpus parameter to
> determine
> > how many to bring online.
> 
> I like the idea of having a vcpus_max

I'll see if Ryan Grimm can dust that one off and resend it.

-- 
Ryan Harper
Software Engineer; Linux Technology Center
IBM Corp., Austin, Tx
(512) 838-9253   T/L: 678-9253
ryanh@us.ibm.com

  reply	other threads:[~2006-08-14 22:46 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-14 22:40 [PATCH 2/3] xend: Add multiple cpumasks support Ian Pratt
2006-08-14 22:46 ` Ryan Harper [this message]
2006-08-16 23:34   ` Ryan Grimm
  -- strict thread matches above, loose matches on Subject: below --
2006-08-17  2:01 Ian Pratt
2006-08-17 15:27 ` Ryan Grimm
2006-08-15 23:26 Ian Pratt
2006-08-16 11:15 ` Subrahmanian, Raj
2006-08-14 22:03 Ian Pratt
2006-08-14 22:20 ` Ryan Harper
2006-08-15  9:07   ` Keir Fraser
2006-08-15 22:58     ` Ryan Harper
2006-08-14 18:55 Ian Pratt
2006-08-14 19:08 ` Ryan Harper
2006-08-14 20:15   ` Ryan Harper
2006-08-14 18:10 Ian Pratt
2006-08-14 18:47 ` Ryan Harper
2006-08-15  8:44   ` Keir Fraser
2006-08-15 23:01     ` Ryan Harper
2006-08-14 16:57 Ryan Harper
2006-08-14 17:37 ` Keir Fraser
2006-08-14 17:48   ` Ryan Harper
2006-08-14 17:55     ` 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=20060814224605.GT1694@us.ibm.com \
    --to=ryanh@us.ibm.com \
    --cc=grimm@us.ibm.com \
    --cc=m+Ian.Pratt@cl.cam.ac.uk \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.