From: Josh Triplett <josht@us.ibm.com>
To: Sean Dague <sean@dague.net>
Cc: xen-tools@lists.xensource.com,
Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>,
xen-devel@lists.xensource.com
Subject: Re: Re: [Xen-tools] [RFC] xm interface proposed changes
Date: Tue, 02 Aug 2005 16:12:01 -0700 [thread overview]
Message-ID: <1123024321.4464.16.camel@localhost.localdomain> (raw)
In-Reply-To: <20050802113246.GA13850@underhill.no-ip.org>
On Tue, 2005-08-02 at 07:32 -0400, Sean Dague wrote:
> On Tue, Aug 02, 2005 at 12:10:48PM +0100, Ian Pratt wrote:
> > > * cpus-set <DomId> <VCpu> <CPUS> Set which cpus a VCPU can use.
> >
> > I'm not sure about this one, but an struggling to think of anything
> > better.
> > cpu-set-affinity ?
>
> Yeh, I was scratching my head a lot on this one too. Trying to brainstorm
> now (help in this regard would be good):
>
> cpu-allocate <DomId> <VCpu> <CPUS>?
> vcpu-set <DomId> <VCpu> <CPUS>?
How about vcpu-pin? "pin" is a relatively common shorthand for setting
affinity.
> > > Commands related to virtual block devices:
> > >
> > > * block-create <DomId> <BackDev> <FrontDev> <Mode>
> > > [BackDomId] Create a new virtual block device for a domain
> > > * block-destroy <DomId> <DevId> Destroy a domain's virtual
> > > block device
> >
> > add/remove (or add/del) might sound a little less brutal than
> > create/destroy.
>
> Yep, good point.
How about attach/detach?
- Josh Triplett
next prev parent reply other threads:[~2005-08-02 23:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-02 11:10 [Xen-tools] [RFC] xm interface proposed changes Ian Pratt
2005-08-02 11:32 ` Sean Dague
2005-08-02 13:12 ` Mark Williamson
2005-08-02 23:12 ` Josh Triplett [this message]
2005-08-02 11:39 ` Daniel Hulme
2005-08-02 13:25 ` Sean Dague
-- strict thread matches above, loose matches on Subject: below --
2005-08-02 14:49 RE: [Xen-tools] " Ian Pratt
2005-08-02 12:07 Ian Pratt
2005-08-02 13:17 ` Mark Williamson
2005-08-02 13:23 ` Sean Dague
2005-07-29 13:04 Sean Dague
2005-07-29 14:25 ` [Xen-tools] " harry
2005-07-29 14:44 ` Sean Dague
2005-07-29 14:54 ` Ronald G. Minnich
2005-07-29 16:18 ` harry
2005-07-29 15:28 ` harry
2005-07-29 17:35 ` Sean Dague
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=1123024321.4464.16.camel@localhost.localdomain \
--to=josht@us.ibm.com \
--cc=m+Ian.Pratt@cl.cam.ac.uk \
--cc=sean@dague.net \
--cc=xen-devel@lists.xensource.com \
--cc=xen-tools@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.