From: "Ky Srinivasan" <ksrinivasan@novell.com>
To: xen-devel@lists.xensource.com, Keir Fraser <keir@xensource.com>
Subject: Re: VCPU affinity
Date: Mon, 18 Dec 2006 10:14:09 -0700 [thread overview]
Message-ID: <4586768D.E57C.0030.0@novell.com> (raw)
In-Reply-To: <C1AC6CC0.6429%keir@xensource.com>
Kier,
Looks like we may have a problem in our tool stack. If I pin the VCPUs from the command line, VCPUs stay bound to the specified physical processors. However, if the binding is specified in the VM config file, it does not work. Looks like we are not correctly handling the CPU affinity information. Will keep you posted once I learn more.
Regards,
K. Y
>>> On Mon, Dec 18, 2006 at 11:05 AM, in message
<C1AC6CC0.6429%keir@xensource.com>, Keir Fraser <keir@xensource.com> wrote:
> VCPUs will run only on CPUs in their affinity mask. If you want to pin to a
> particular CPU then specify an affinity mask with only that CPU contained in
> it.
>
> -- Keir
>
>
> On 18/12/06 15:56, "Ky Srinivasan" <ksrinivasan@novell.com> wrote:
>
>> What is the best way to pin VCPUs. It looks like the implementation of
>> affinity currently is at best only "soft".
>>
>> Regards,
>>
>> K. Y
>>
>>
>> _______________________________________________
>> Xen- devel mailing list
>> Xen- devel@lists.xensource.com
>> http://lists.xensource.com/xen- devel
>
>
> _______________________________________________
> Xen- devel mailing list
> Xen- devel@lists.xensource.com
> http://lists.xensource.com/xen- devel
prev parent reply other threads:[~2006-12-18 17:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-18 15:56 VCPU affinity Ky Srinivasan
2006-12-18 16:01 ` Emmanuel Ackaouy
2006-12-18 17:08 ` Ky Srinivasan
2006-12-18 16:05 ` Keir Fraser
2006-12-18 17:14 ` Ky Srinivasan [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=4586768D.E57C.0030.0@novell.com \
--to=ksrinivasan@novell.com \
--cc=keir@xensource.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 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.