From: Dario Faggioli <dfaggioli@suse.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: Juergen Gross <jgross@suse.com>,
xen-devel@lists.xenproject.org,
George Dunlap <george.dunlap@citrix.com>,
Andrew Cooper <andrew.cooper3@citrix.com>
Subject: Re: [PATCH 2/2] xen: credit2: limit the max number of CPUs in a runqueue
Date: Fri, 29 May 2020 12:19:21 +0200 [thread overview]
Message-ID: <d95076bab67035437d1e055c76adf4ad824b81e8.camel@suse.com> (raw)
In-Reply-To: <bc005ca2-7bf2-3bb0-b9cd-0be05c914f3f@suse.com>
[-- Attachment #1: Type: text/plain, Size: 1150 bytes --]
On Fri, 2020-05-29 at 11:58 +0200, Jan Beulich wrote:
> On 28.05.2020 16:55, Dario Faggioli wrote:
> >
> > Which means I will be treating HTs and CUs the same which, thinking
> > more about it (and thinking actually to CUs, rather than to any
> > cache
> > sharing relationship), does make sense for this feature.
> >
> > Does this make sense, or am I missing or misinterpreting anything?
>
> Well, it effectively answers the question I had raised: "What about
> HT
> vs AMD Fam15's CUs? Do you want both to be treated the same here?"
>
Exactly! :-)
And, in fact, the answer is "Yes, I want them being treated the same,
and the patches are actually doing ".
Sorry for not getting it right away, and just replying like that in the
first place.
At least, this led to better (more generic) comments and variable names
in v2 of this patch.
Regards
--
Dario Faggioli, Ph.D
http://about.me/dario.faggioli
Virtualization Software Engineer
SUSE Labs, SUSE https://www.suse.com/
-------------------------------------------------------------------
<<This happens because _I_ choose it to happen!>> (Raistlin Majere)
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-05-29 10:19 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-29 17:36 [PATCH 0/2] xen: credit2: limit the number of CPUs per runqueue Dario Faggioli
2020-04-29 17:36 ` [PATCH 1/2] xen: credit2: factor cpu to runqueue matching in a function Dario Faggioli
2020-04-29 17:36 ` [PATCH 2/2] xen: credit2: limit the max number of CPUs in a runqueue Dario Faggioli
2020-04-30 6:45 ` Jan Beulich
2020-05-26 22:00 ` Dario Faggioli
2020-05-27 4:26 ` Jürgen Groß
2020-05-28 9:32 ` Dario Faggioli
2020-05-27 6:17 ` Jan Beulich
2020-05-28 14:55 ` Dario Faggioli
2020-05-29 9:58 ` Jan Beulich
2020-05-29 10:19 ` Dario Faggioli [this message]
2020-04-30 7:35 ` Jürgen Groß
2020-04-30 12:28 ` Dario Faggioli
2020-04-30 12:52 ` Jürgen Groß
2020-04-30 14:01 ` Dario Faggioli
2020-05-26 21:18 ` Dario Faggioli
2020-05-27 6:22 ` Jan Beulich
2020-05-28 9:36 ` Dario Faggioli
2020-05-29 11:46 ` [PATCH 0/2] xen: credit2: limit the number of CPUs per runqueue Dario Faggioli
2020-05-29 15:06 ` Dario Faggioli
2020-05-29 16:15 ` George Dunlap
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=d95076bab67035437d1e055c76adf4ad824b81e8.camel@suse.com \
--to=dfaggioli@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=george.dunlap@citrix.com \
--cc=jbeulich@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).