From: Dietmar Eggemann <dietmar.eggemann@arm.com>
To: Barry Song <song.bao.hua@hisilicon.com>,
valentin.schneider@arm.com, catalin.marinas@arm.com,
will@kernel.org, rjw@rjwysocki.net, lenb@kernel.org,
gregkh@linuxfoundation.org, Jonathan.Cameron@huawei.com,
mingo@redhat.com, peterz@infradead.org, juri.lelli@redhat.com,
vincent.guittot@linaro.org, rostedt@goodmis.org,
bsegall@google.com, mgorman@suse.de, mark.rutland@arm.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org
Cc: linuxarm@huawei.com, xuwei5@huawei.com, prime.zeng@hisilicon.com
Subject: Re: [RFC PATCH v2 0/2] scheduler: expose the topology of clusters and add cluster scheduler
Date: Tue, 1 Dec 2020 11:46:20 +0100 [thread overview]
Message-ID: <fb332889-6385-fe23-be12-5caf150d5817@arm.com> (raw)
In-Reply-To: <20201201025944.18260-1-song.bao.hua@hisilicon.com>
On 01/12/2020 03:59, Barry Song wrote:
[...]
> Although I believe there is still a lot to do, sending a RFC to get feedbacks
> of community experts might be helpful for the next step.
>
> Barry Song (1):
> scheduler: add scheduler level for clusters
>
> Jonathan Cameron (1):
> topology: Represent clusters of CPUs within a die.
Just to make sure. Since this is v2, the v1 is
https://lkml.kernel.org/r//20201016152702.1513592-1-Jonathan.Cameron@huawei.com
Might not be obvious to everyone since sender and subject have changed.
prev parent reply other threads:[~2020-12-01 10:47 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-01 2:59 [RFC PATCH v2 0/2] scheduler: expose the topology of clusters and add cluster scheduler Barry Song
2020-12-01 2:59 ` [RFC PATCH v2 1/2] topology: Represent clusters of CPUs within a die Barry Song
2020-12-01 16:03 ` Valentin Schneider
2020-12-02 9:55 ` Sudeep Holla
2020-12-01 2:59 ` [RFC PATCH v2 2/2] scheduler: add scheduler level for clusters Barry Song
2020-12-01 16:04 ` Valentin Schneider
2020-12-03 9:28 ` Peter Zijlstra
2020-12-03 9:49 ` Mel Gorman
2020-12-03 9:57 ` Song Bao Hua (Barry Song)
2020-12-03 10:07 ` Peter Zijlstra
2020-12-02 8:27 ` Vincent Guittot
2020-12-02 9:20 ` Song Bao Hua (Barry Song)
2020-12-02 10:16 ` Vincent Guittot
2020-12-02 10:45 ` Song Bao Hua (Barry Song)
2020-12-02 10:48 ` Song Bao Hua (Barry Song)
2020-12-02 20:58 ` Song Bao Hua (Barry Song)
2020-12-03 9:03 ` Vincent Guittot
2020-12-03 9:11 ` Song Bao Hua (Barry Song)
2020-12-03 9:39 ` Vincent Guittot
2020-12-03 9:54 ` Vincent Guittot
2020-12-07 9:59 ` Song Bao Hua (Barry Song)
2020-12-07 15:29 ` Vincent Guittot
2020-12-09 11:35 ` Song Bao Hua (Barry Song)
2020-12-01 10:46 ` Dietmar Eggemann [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=fb332889-6385-fe23-be12-5caf150d5817@arm.com \
--to=dietmar.eggemann@arm.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=bsegall@google.com \
--cc=catalin.marinas@arm.com \
--cc=gregkh@linuxfoundation.org \
--cc=juri.lelli@redhat.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=mark.rutland@arm.com \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=prime.zeng@hisilicon.com \
--cc=rjw@rjwysocki.net \
--cc=rostedt@goodmis.org \
--cc=song.bao.hua@hisilicon.com \
--cc=valentin.schneider@arm.com \
--cc=vincent.guittot@linaro.org \
--cc=will@kernel.org \
--cc=xuwei5@huawei.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).