From: Keir Fraser <keir.fraser@eu.citrix.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: Juergen Gross <juergen.gross@ts.fujitsu.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [Patch] use full-size cpumask for vcpu-pin
Date: Fri, 13 Aug 2010 15:09:30 +0100 [thread overview]
Message-ID: <C88B10AA.1DB83%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <C88B078B.1DB63%keir.fraser@eu.citrix.com>
On 13/08/2010 14:30, "Keir Fraser" <keir.fraser@eu.citrix.com> wrote:
>> One suggestion: that we rename the syctl.physinfo field 'max_phys_cpus' to
>> 'max_possible_cpus'. The 'phys' is kind of redundant since this is the
>> physinfo sysctl, and 'possible' provides a better hint that this fields
>> indicates maximum possible supported CPUs now and forever on this boot of
>> the system.
>
> Even better, let's not introduce a new field at all, and let's always set
> sysctl.phys_info.max_cpu_id to NR_CPUS-1. Then I don't think any tools
> changes are needed.
>
> Yeah, that's what we should do. I will make a patch for that.
Done as xen-unstable:f6e1a597a92f. At this late stage it's probably a bit
too subtle for backport to 4.0.1 unfortunately (I hate to wonder if there
could be subtle side effects on xend's usage of these max_*_id fields).
-- Keir
> -- Keir
>
>> -- Keir
>>
>
prev parent reply other threads:[~2010-08-13 14:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-02 6:40 [Patch] use full-size cpumask for vcpu-pin Juergen Gross
2010-08-10 14:11 ` Ian Jackson
2010-08-10 14:27 ` Keir Fraser
2010-08-11 4:32 ` Juergen Gross
2010-08-13 12:31 ` Ian Jackson
2010-08-13 12:58 ` Keir Fraser
2010-08-13 13:11 ` Ian Jackson
2010-08-13 13:15 ` Keir Fraser
2010-08-13 13:21 ` Keir Fraser
2010-08-13 13:25 ` Keir Fraser
2010-08-13 13:29 ` Ian Jackson
2010-08-13 13:30 ` Keir Fraser
2010-08-13 14:09 ` 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=C88B10AA.1DB83%keir.fraser@eu.citrix.com \
--to=keir.fraser@eu.citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=juergen.gross@ts.fujitsu.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).