From: Dario Faggioli <dfaggioli@suse.com>
To: Juergen Gross <jgross@suse.com>, xen-devel@lists.xenproject.org
Subject: Re: [PATCH] xen: cpupool: forbid to split cores among different pools
Date: Tue, 21 Aug 2018 10:43:26 +0200 [thread overview]
Message-ID: <971a220c99fb911e6ce0234f5fbaf518216500c0.camel@suse.com> (raw)
In-Reply-To: <3b093873-2534-d591-de50-8921e5b7f8ff@suse.com>
[-- Attachment #1.1: Type: text/plain, Size: 909 bytes --]
On Tue, 2018-08-21 at 10:25 +0200, Juergen Gross wrote:
> On 20/08/18 18:43, Dario Faggioli wrote:
> >
> > Therefore, let's start allowing in a cpupool only cpus that have
> > their
> > SMT siblings, either:
> > - in that same pool,
> > - outside of any pool.
>
> Can we make this optional somehow? I don't mind this behavior to be
> the
> default, but it should be possible to switch it off.
>
Yeah, I was thinking to that too. I guess we can add a 'force'
bit/flag. Let me look into that.
> Otherwise it will be impossible e.g. to test moving cpus between two
> cpupools on a machine with only 2 cores.
>
Yep, good point!
Regards,
Dario
--
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Software Engineer @ SUSE https://www.suse.com/
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 157 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
prev parent reply other threads:[~2018-08-21 8:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-20 16:43 [PATCH] xen: cpupool: forbid to split cores among different pools Dario Faggioli
2018-08-21 8:25 ` Juergen Gross
2018-08-21 8:43 ` Dario Faggioli [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=971a220c99fb911e6ce0234f5fbaf518216500c0.camel@suse.com \
--to=dfaggioli@suse.com \
--cc=jgross@suse.com \
--cc=xen-devel@lists.xenproject.org \
/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).