RE: [RFC PATCH v5 4/4] scheduler: Add cluster scheduler level for x86

2021-04-20 Thread Song Bao Hua (Barry Song)
inux...@openeuler.org; h...@zytor.com > Subject: Re: [RFC PATCH v5 4/4] scheduler: Add cluster scheduler level for x86 > > > > On 3/23/21 4:21 PM, Song Bao Hua (Barry Song) wrote: > > >> > >> On 3/18/21 9:16 PM, Barry Song wrote: > >>> From: Tim

Re: [RFC PATCH v5 4/4] scheduler: Add cluster scheduler level for x86

2021-04-20 Thread Tim Chen
On 3/23/21 4:21 PM, Song Bao Hua (Barry Song) wrote: >> >> On 3/18/21 9:16 PM, Barry Song wrote: >>> From: Tim Chen >>> >>> There are x86 CPU architectures (e.g. Jacobsville) where L2 cahce >>> is shared among a cluster of cores instead of being exclusive >>> to one single core. >>> >>> To

RE: [RFC PATCH v5 4/4] scheduler: Add cluster scheduler level for x86

2021-03-31 Thread Song Bao Hua (Barry Song)
> linux-kernel@vger.kernel.org; linux-a...@vger.kernel.org; x...@kernel.org; > > xuwei (O) ; Zengtao (B) ; > > guodong...@linaro.org; yangyicong ; Liguozhu > (Kenneth) > > ; linux...@openeuler.org; h...@zytor.com > > Subject: Re: [RFC PATCH v5 4/4] scheduler: Add cluster sched

RE: [RFC PATCH v5 4/4] scheduler: Add cluster scheduler level for x86

2021-03-23 Thread Song Bao Hua (Barry Song)
inux...@openeuler.org; h...@zytor.com > Subject: Re: [RFC PATCH v5 4/4] scheduler: Add cluster scheduler level for x86 > > > > On 3/18/21 9:16 PM, Barry Song wrote: > > From: Tim Chen > > > > There are x86 CPU architectures (e.g. Jacobsville) where L2 cahce >

Re: [RFC PATCH v5 4/4] scheduler: Add cluster scheduler level for x86

2021-03-23 Thread Tim Chen
On 3/18/21 9:16 PM, Barry Song wrote: > From: Tim Chen > > There are x86 CPU architectures (e.g. Jacobsville) where L2 cahce > is shared among a cluster of cores instead of being exclusive > to one single core. > > To prevent oversubscription of L2 cache, load should be > balanced between

[RFC PATCH v5 4/4] scheduler: Add cluster scheduler level for x86

2021-03-18 Thread Barry Song
From: Tim Chen There are x86 CPU architectures (e.g. Jacobsville) where L2 cahce is shared among a cluster of cores instead of being exclusive to one single core. To prevent oversubscription of L2 cache, load should be balanced between such L2 clusters, especially for tasks with no shared data.