All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: 王擎 <wangqing@vivo.com>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will@kernel.org>,
	Sudeep Holla <sudeep.holla@arm.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	"Rafael J. Wysocki" <rafael@kernel.org>,
	Ingo Molnar <mingo@redhat.com>,
	Juri Lelli <juri.lelli@redhat.com>,
	Vincent Guittot <vincent.guittot@linaro.org>,
	Dietmar Eggemann <dietmar.eggemann@arm.com>,
	Steven Rostedt <rostedt@goodmis.org>,
	Ben Segall <bsegall@google.com>, Mel Gorman <mgorman@suse.de>,
	Daniel Bristot de Oliveira <bristot@redhat.com>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] sched: topology: make cache topology separate from cpu topology
Date: Mon, 14 Mar 2022 11:19:12 +0100	[thread overview]
Message-ID: <Yi8WoC40tb8ulrmd@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <SL2PR06MB3082047700A8440BD0DE80DEBD0F9@SL2PR06MB3082.apcprd06.prod.outlook.com>

On Mon, Mar 14, 2022 at 02:37:48AM +0000, 王擎 wrote:

> > If you want to represent L2, use the new fangled cluster level or
> > something, that's what it's there for.
> > 
> > That is, you can represent the above like:
> > 
> >        DIE:    0-7
> >        MC:     0-3,            4-7
> >         CLS:    0-1,1-2,        4-5,6-7
> > 
> > But if there is cache at MC, LLC is what it is.
> 
> There is no CLS support for LTS now, any plans to backport?

-ENOTMYPROBLEM

WARNING: multiple messages have this Message-ID (diff)
From: Peter Zijlstra <peterz@infradead.org>
To: 王擎 <wangqing@vivo.com>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will@kernel.org>,
	Sudeep Holla <sudeep.holla@arm.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	"Rafael J. Wysocki" <rafael@kernel.org>,
	Ingo Molnar <mingo@redhat.com>,
	Juri Lelli <juri.lelli@redhat.com>,
	Vincent Guittot <vincent.guittot@linaro.org>,
	Dietmar Eggemann <dietmar.eggemann@arm.com>,
	Steven Rostedt <rostedt@goodmis.org>,
	Ben Segall <bsegall@google.com>, Mel Gorman <mgorman@suse.de>,
	Daniel Bristot de Oliveira <bristot@redhat.com>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	 "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] sched: topology: make cache topology separate from cpu topology
Date: Mon, 14 Mar 2022 11:19:12 +0100	[thread overview]
Message-ID: <Yi8WoC40tb8ulrmd@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <SL2PR06MB3082047700A8440BD0DE80DEBD0F9@SL2PR06MB3082.apcprd06.prod.outlook.com>

On Mon, Mar 14, 2022 at 02:37:48AM +0000, 王擎 wrote:

> > If you want to represent L2, use the new fangled cluster level or
> > something, that's what it's there for.
> > 
> > That is, you can represent the above like:
> > 
> >        DIE:    0-7
> >        MC:     0-3,            4-7
> >         CLS:    0-1,1-2,        4-5,6-7
> > 
> > But if there is cache at MC, LLC is what it is.
> 
> There is no CLS support for LTS now, any plans to backport?

-ENOTMYPROBLEM

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2022-03-14 10:19 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-10 12:58 [PATCH] sched: topology: make cache topology separate from cpu topology Qing Wang
2022-03-10 12:58 ` Qing Wang
2022-03-10 14:18 ` Vincent Guittot
2022-03-10 14:18   ` Vincent Guittot
2022-03-11  2:03   ` 王擎
2022-03-11  2:03     ` 王擎
2022-03-11  7:59     ` Vincent Guittot
2022-03-11  7:59       ` Vincent Guittot
2022-03-11  8:18       ` 王擎
2022-03-11  8:18         ` 王擎
2022-03-11  8:25         ` Vincent Guittot
2022-03-11  8:25           ` Vincent Guittot
2022-03-11  9:30           ` 王擎
2022-03-11  9:30             ` 王擎
2022-03-11 11:14             ` Vincent Guittot
2022-03-11 11:14               ` Vincent Guittot
2022-03-15  1:58               ` 王擎
2022-03-15  1:58                 ` 王擎
2022-03-15 16:51                 ` Vincent Guittot
2022-03-15 16:51                   ` Vincent Guittot
2022-04-02  9:34                   ` 王擎
2022-04-02  9:34                     ` 王擎
2022-04-02 10:29                     ` Yicong Yang
2022-04-02 10:29                       ` Yicong Yang
2022-04-04 12:31                     ` Vincent Guittot
2022-04-04 12:31                       ` Vincent Guittot
2022-04-07  2:31                       ` 王擎
2022-04-07  2:31                         ` 王擎
2022-03-10 17:35 ` kernel test robot
2022-03-10 17:35   ` kernel test robot
2022-03-11 11:24 ` Peter Zijlstra
2022-03-11 11:24   ` Peter Zijlstra
2022-03-14  2:37   ` 王擎
2022-03-14  2:37     ` 王擎
2022-03-14 10:19     ` Peter Zijlstra [this message]
2022-03-14 10:19       ` Peter Zijlstra

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=Yi8WoC40tb8ulrmd@hirez.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=bristot@redhat.com \
    --cc=bsegall@google.com \
    --cc=catalin.marinas@arm.com \
    --cc=dietmar.eggemann@arm.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=juri.lelli@redhat.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mgorman@suse.de \
    --cc=mingo@redhat.com \
    --cc=rafael@kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=sudeep.holla@arm.com \
    --cc=vincent.guittot@linaro.org \
    --cc=wangqing@vivo.com \
    --cc=will@kernel.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.