From: Tim Chen <tim.c.chen@linux.intel.com>
To: Phil Auld <pauld@redhat.com>
Cc: Vincent Guittot <vincent.guittot@linaro.org>,
"Li, Aubrey" <aubrey.li@linux.intel.com>,
Mel Gorman <mgorman@suse.de>, Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Juri Lelli <juri.lelli@redhat.com>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Steven Rostedt <rostedt@goodmis.org>,
Ben Segall <bsegall@google.com>,
Valentin Schneider <valentin.schneider@arm.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
Qais Yousef <qais.yousef@arm.com>,
Jiang Biao <benbjiang@gmail.com>
Subject: Re: [RFC PATCH v2] sched/fair: select idle cpu from idle cpumask in sched domain
Date: Thu, 24 Sep 2020 10:43:12 -0700 [thread overview]
Message-ID: <129fceda-cf89-de74-f3fd-026c3c089d62@linux.intel.com> (raw)
In-Reply-To: <20200924171339.GD29958@lorien.usersys.redhat.com>
On 9/24/20 10:13 AM, Phil Auld wrote:
> On Thu, Sep 24, 2020 at 09:37:33AM -0700 Tim Chen wrote:
>>
>>
>> On 9/22/20 12:14 AM, Vincent Guittot wrote:
>>
>>>>
>>>>>>
>>>>>> And a quick test with hackbench on my octo cores arm64 gives for 12
>>
>> Vincent,
>>
>> Is it octo (=10) or octa (=8) cores on a single socket for your system?
>
> In what Romance language does octo mean 10? :)
>
Got confused by october, the tenth month. :)
Tim
>
>> The L2 is per core or there are multiple L2s shared among groups of cores?
>>
>> Wonder if placing the threads within a L2 or not within
>> an L2 could cause differences seen with Aubrey's test.
>>
>> Tim
>>
>
next prev parent reply other threads:[~2020-09-24 17:43 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-16 4:31 [RFC PATCH v2] sched/fair: select idle cpu from idle cpumask in sched domain Aubrey Li
2020-09-16 11:00 ` Mel Gorman
2020-09-16 11:40 ` Valentin Schneider
2020-09-16 12:04 ` Vincent Guittot
2020-09-17 9:21 ` Li, Aubrey
2020-09-21 15:14 ` Vincent Guittot
2020-09-21 15:21 ` Vincent Guittot
[not found] ` <af0237e0-1451-9d11-2ee2-1468a8bb6180@linux.intel.com>
2020-09-22 7:14 ` Vincent Guittot
[not found] ` <8a86b085-b445-b1c2-9b46-6346d923abf0@linux.intel.com>
2020-09-23 8:50 ` Vincent Guittot
[not found] ` <eb1c4c84-e361-d5a7-d071-b0dd7310eab4@linux.intel.com>
2020-09-24 13:09 ` Vincent Guittot
2020-09-25 9:21 ` Li, Aubrey
2020-09-25 16:45 ` Vincent Guittot
2020-09-27 5:56 ` Li, Aubrey
2020-09-24 16:37 ` Tim Chen
2020-09-24 17:13 ` Phil Auld
2020-09-24 17:43 ` Tim Chen [this message]
2020-09-24 17:45 ` Phil Auld
2020-09-25 6:50 ` Vincent Guittot
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=129fceda-cf89-de74-f3fd-026c3c089d62@linux.intel.com \
--to=tim.c.chen@linux.intel.com \
--cc=aubrey.li@linux.intel.com \
--cc=benbjiang@gmail.com \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=pauld@redhat.com \
--cc=peterz@infradead.org \
--cc=qais.yousef@arm.com \
--cc=rostedt@goodmis.org \
--cc=valentin.schneider@arm.com \
--cc=vincent.guittot@linaro.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).