[Re: [PATCH RFC cpumask] Allow "all", "none", and "last" in cpumask strings] On
20/01/2021 (Wed 23:11) Yury Norov wrote:
> Hi Paul,
>
> Today I found this series in linux-next despite downsides discovered during
> the review. This series introduce
On Thu, Jan 21, 2021 at 08:57:25AM -0800, Paul E. McKenney wrote:
> On Wed, Jan 20, 2021 at 11:11:48PM -0800, Yury Norov wrote:
> > On Wed, Jan 6, 2021 at 12:49 AM Yury Norov wrote:
> > >
> > > On Tue, Jan 5, 2021 at 4:48 PM Paul E. McKenney
> > > wrote:
> > > >
> > > > Hello!
> > > >
> > > > Th
On Wed, Jan 20, 2021 at 11:11:48PM -0800, Yury Norov wrote:
> On Wed, Jan 6, 2021 at 12:49 AM Yury Norov wrote:
> >
> > On Tue, Jan 5, 2021 at 4:48 PM Paul E. McKenney wrote:
> > >
> > > Hello!
> > >
> > > This series allows "all", "none", and "last" to be used in cpumask
> > > strings. This all
On Wed, Jan 6, 2021 at 12:49 AM Yury Norov wrote:
>
> On Tue, Jan 5, 2021 at 4:48 PM Paul E. McKenney wrote:
> >
> > Hello!
> >
> > This series allows "all", "none", and "last" to be used in cpumask
> > strings. This allows these strings to be less dependent on the underlying
> > system. For ex
On Tue, Jan 5, 2021 at 4:48 PM Paul E. McKenney wrote:
>
> Hello!
>
> This series allows "all", "none", and "last" to be used in cpumask
> strings. This allows these strings to be less dependent on the underlying
> system. For example, currently a string specifying all but the first
> CPU must b
Hello!
This series allows "all", "none", and "last" to be used in cpumask
strings. This allows these strings to be less dependent on the underlying
system. For example, currently a string specifying all but the first
CPU must be "1-7" on an eight-CPU system and "1-15" on a 16-CPU system.
With th
6 matches
Mail list logo