All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jürgen Groß" <jgross@suse.com>
To: Dario Faggioli <dfaggioli@suse.com>, xen-devel@lists.xenproject.org
Cc: George Dunlap <george.dunlap@citrix.com>
Subject: Re: [PATCH v2 3/7] xen: cpupool: add a back-pointer from a scheduler to its pool
Date: Fri, 29 May 2020 16:54:12 +0200	[thread overview]
Message-ID: <01541fda-c7dc-1eac-7184-970244eaf505@suse.com> (raw)
In-Reply-To: <159070137738.12060.10928971799525755388.stgit@Palanthas>

On 28.05.20 23:29, Dario Faggioli wrote:
> If we need to know within which pool a particular scheduler
> is working, we can do that by querying the cpupool pointer
> of any of the sched_resource-s (i.e., ~ any of the CPUs)
> assigned to the scheduler itself.
> 
> Basically, we pick any sched_resource that we know uses that
> scheduler, and we check its *cpupool pointer. If we really
> know that the resource uses the scheduler, this is fine, as
> it also means the resource is inside the pool we are
> looking for.
> 
> But, of course, we can do that for a pool/scheduler that has

s/can/can't/ ?

> not any been given any sched_resource yet (or if we do not
> know whether or not it has any sched_resource).
> 
> To overcome such limitation, add a back pointer from the
> scheduler, to its own pool.
> 
> Signed-off-by: Dario Faggioli <dfaggioli@suse.com>

Reviewed-by: Juergen Gross <jgross@suse.com>


Juergen


  reply	other threads:[~2020-05-29 14:54 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-28 21:29 [PATCH v2 0/7] xen: credit2: limit the number of CPUs per runqueue Dario Faggioli
2020-05-28 21:29 ` [PATCH v2 1/7] xen: credit2: factor cpu to runqueue matching in a function Dario Faggioli
2020-05-29 14:48   ` Jürgen Groß
2020-05-28 21:29 ` [PATCH v2 2/7] xen: credit2: factor runqueue initialization in its own function Dario Faggioli
2020-05-29 14:50   ` Jürgen Groß
2020-05-28 21:29 ` [PATCH v2 3/7] xen: cpupool: add a back-pointer from a scheduler to its pool Dario Faggioli
2020-05-29 14:54   ` Jürgen Groß [this message]
2020-05-29 14:56     ` Dario Faggioli
2020-05-28 21:29 ` [PATCH v2 4/7] xen: credit2: limit the max number of CPUs in a runqueue Dario Faggioli
2020-05-29 15:23   ` Jürgen Groß
2020-05-29 15:36     ` Dario Faggioli
2020-05-28 21:29 ` [PATCH v2 5/7] xen: credit2: compute cpus per-runqueue more dynamically Dario Faggioli
2020-05-28 21:29 ` [PATCH v2 6/7] cpupool: create an the 'cpupool sync' infrastructure Dario Faggioli
2020-05-28 21:30 ` [PATCH v2 7/7] xen: credit2: rebalance the number of CPUs in the scheduler runqueues Dario Faggioli
2020-07-21 12:08 ` [PATCH v2 0/7] xen: credit2: limit the number of CPUs per runqueue Jan Beulich
2020-07-22 15:33   ` Dario Faggioli

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=01541fda-c7dc-1eac-7184-970244eaf505@suse.com \
    --to=jgross@suse.com \
    --cc=dfaggioli@suse.com \
    --cc=george.dunlap@citrix.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 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.