On Thu, 18 Jan 2018 04:04:43 +0100
Frederic Weisbecker wrote:
> On Wed, Jan 17, 2018 at 12:38:01PM -0500, Luiz Capitulino wrote:
> > On Tue, 16 Jan 2018 23:51:29 +0100
> > Frederic Weisbecker wrote:
> >
> > > On Tue, Jan 16, 2018 at 11:52:11AM -0500,
On Thu, 18 Jan 2018 04:04:43 +0100
Frederic Weisbecker wrote:
> On Wed, Jan 17, 2018 at 12:38:01PM -0500, Luiz Capitulino wrote:
> > On Tue, 16 Jan 2018 23:51:29 +0100
> > Frederic Weisbecker wrote:
> >
> > > On Tue, Jan 16, 2018 at 11:52:11AM -0500, Luiz Capitulino wrote:
> > > > On Tue,
On Wed, Jan 17, 2018 at 12:38:01PM -0500, Luiz Capitulino wrote:
> On Tue, 16 Jan 2018 23:51:29 +0100
> Frederic Weisbecker wrote:
>
> > On Tue, Jan 16, 2018 at 11:52:11AM -0500, Luiz Capitulino wrote:
> > > On Tue, 16 Jan 2018 16:41:00 +0100
> > > Frederic Weisbecker
On Wed, Jan 17, 2018 at 12:38:01PM -0500, Luiz Capitulino wrote:
> On Tue, 16 Jan 2018 23:51:29 +0100
> Frederic Weisbecker wrote:
>
> > On Tue, Jan 16, 2018 at 11:52:11AM -0500, Luiz Capitulino wrote:
> > > On Tue, 16 Jan 2018 16:41:00 +0100
> > > Frederic Weisbecker wrote:
> > > > So
On Tue, 16 Jan 2018 23:51:29 +0100
Frederic Weisbecker wrote:
> On Tue, Jan 16, 2018 at 11:52:11AM -0500, Luiz Capitulino wrote:
> > On Tue, 16 Jan 2018 16:41:00 +0100
> > Frederic Weisbecker wrote:
> > > So isolcpus= is now the place where we control
On Tue, 16 Jan 2018 23:51:29 +0100
Frederic Weisbecker wrote:
> On Tue, Jan 16, 2018 at 11:52:11AM -0500, Luiz Capitulino wrote:
> > On Tue, 16 Jan 2018 16:41:00 +0100
> > Frederic Weisbecker wrote:
> > > So isolcpus= is now the place where we control the isolation features
> > > and nohz is
On Wed, 2018-01-17 at 10:32 -0600, Christopher Lameter wrote:
> On Wed, 17 Jan 2018, Mike Galbraith wrote:
>
> > Domain connectivity very much is a property of a set of CPUs, a rather
> > important one, and one managed by cpusets. NOHZ_FULL is a property of
> > a set of cpus, thus a most
On Wed, 2018-01-17 at 10:32 -0600, Christopher Lameter wrote:
> On Wed, 17 Jan 2018, Mike Galbraith wrote:
>
> > Domain connectivity very much is a property of a set of CPUs, a rather
> > important one, and one managed by cpusets. NOHZ_FULL is a property of
> > a set of cpus, thus a most
On Wed, 17 Jan 2018, Mike Galbraith wrote:
> Domain connectivity very much is a property of a set of CPUs, a rather
> important one, and one managed by cpusets. NOHZ_FULL is a property of
> a set of cpus, thus a most excellent fit. Other things are as well.
Not sure to what domain refers to in
On Wed, 17 Jan 2018, Mike Galbraith wrote:
> Domain connectivity very much is a property of a set of CPUs, a rather
> important one, and one managed by cpusets. NOHZ_FULL is a property of
> a set of cpus, thus a most excellent fit. Other things are as well.
Not sure to what domain refers to in
On Wed, 2018-01-17 at 08:51 -0600, Christopher Lameter wrote:
> On Tue, 16 Jan 2018, Mike Galbraith wrote:
>
> > > I tried to remove isolcpus or at least change the way it works so that its
> > > effects are reversible (ie: affine the init task instead of isolating
> > > domains)
> > > but that
On Wed, 2018-01-17 at 08:51 -0600, Christopher Lameter wrote:
> On Tue, 16 Jan 2018, Mike Galbraith wrote:
>
> > > I tried to remove isolcpus or at least change the way it works so that its
> > > effects are reversible (ie: affine the init task instead of isolating
> > > domains)
> > > but that
On Tue, 16 Jan 2018, Mike Galbraith wrote:
> > I tried to remove isolcpus or at least change the way it works so that its
> > effects are reversible (ie: affine the init task instead of isolating
> > domains)
> > but that got nacked due to the behaviour's expectations for userspace.
>
> So we
On Tue, 16 Jan 2018, Mike Galbraith wrote:
> > I tried to remove isolcpus or at least change the way it works so that its
> > effects are reversible (ie: affine the init task instead of isolating
> > domains)
> > but that got nacked due to the behaviour's expectations for userspace.
>
> So we
On Tue, Jan 16, 2018 at 06:58:18PM +0100, Mike Galbraith wrote:
> On Tue, 2018-01-16 at 16:41 +0100, Frederic Weisbecker wrote:
> > On Fri, Jan 12, 2018 at 02:18:13PM -0500, Luiz Capitulino wrote:
> >
> > > Why are extending isolcpus= given that it's a deprecated interface?
> > > Some people have
On Tue, Jan 16, 2018 at 06:58:18PM +0100, Mike Galbraith wrote:
> On Tue, 2018-01-16 at 16:41 +0100, Frederic Weisbecker wrote:
> > On Fri, Jan 12, 2018 at 02:18:13PM -0500, Luiz Capitulino wrote:
> >
> > > Why are extending isolcpus= given that it's a deprecated interface?
> > > Some people have
On Tue, Jan 16, 2018 at 11:52:11AM -0500, Luiz Capitulino wrote:
> On Tue, 16 Jan 2018 16:41:00 +0100
> Frederic Weisbecker wrote:
> > So isolcpus= is now the place where we control the isolation features
> > and nohz is one of them.
>
> That's the part I'm not very sure
On Tue, Jan 16, 2018 at 11:52:11AM -0500, Luiz Capitulino wrote:
> On Tue, 16 Jan 2018 16:41:00 +0100
> Frederic Weisbecker wrote:
> > So isolcpus= is now the place where we control the isolation features
> > and nohz is one of them.
>
> That's the part I'm not very sure about. We've been
On Tue, 2018-01-16 at 16:41 +0100, Frederic Weisbecker wrote:
> On Fri, Jan 12, 2018 at 02:18:13PM -0500, Luiz Capitulino wrote:
>
> > Why are extending isolcpus= given that it's a deprecated interface?
> > Some people have already moved away from isolcpus= now, but with this
> > new feature they
On Tue, 2018-01-16 at 16:41 +0100, Frederic Weisbecker wrote:
> On Fri, Jan 12, 2018 at 02:18:13PM -0500, Luiz Capitulino wrote:
>
> > Why are extending isolcpus= given that it's a deprecated interface?
> > Some people have already moved away from isolcpus= now, but with this
> > new feature they
On Tue, 16 Jan 2018 16:41:00 +0100
Frederic Weisbecker wrote:
> On Fri, Jan 12, 2018 at 02:18:13PM -0500, Luiz Capitulino wrote:
> > On Thu, 4 Jan 2018 05:25:32 +0100
> > Frederic Weisbecker wrote:
> >
> > > Ingo,
> > >
> > > Please pull the
On Tue, 16 Jan 2018 16:41:00 +0100
Frederic Weisbecker wrote:
> On Fri, Jan 12, 2018 at 02:18:13PM -0500, Luiz Capitulino wrote:
> > On Thu, 4 Jan 2018 05:25:32 +0100
> > Frederic Weisbecker wrote:
> >
> > > Ingo,
> > >
> > > Please pull the sched/0hz branch that can be found at:
> > >
>
On Fri, Jan 12, 2018 at 02:18:13PM -0500, Luiz Capitulino wrote:
> On Thu, 4 Jan 2018 05:25:32 +0100
> Frederic Weisbecker wrote:
>
> > Ingo,
> >
> > Please pull the sched/0hz branch that can be found at:
> >
> >
On Fri, Jan 12, 2018 at 02:18:13PM -0500, Luiz Capitulino wrote:
> On Thu, 4 Jan 2018 05:25:32 +0100
> Frederic Weisbecker wrote:
>
> > Ingo,
> >
> > Please pull the sched/0hz branch that can be found at:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/frederic/linux-dynticks.git
> >
On Thu, 4 Jan 2018 05:25:32 +0100
Frederic Weisbecker wrote:
> Ingo,
>
> Please pull the sched/0hz branch that can be found at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/frederic/linux-dynticks.git
> sched/0hz
>
> HEAD:
On Thu, 4 Jan 2018 05:25:32 +0100
Frederic Weisbecker wrote:
> Ingo,
>
> Please pull the sched/0hz branch that can be found at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/frederic/linux-dynticks.git
> sched/0hz
>
> HEAD: 9e932b2cc707209febd130978a5eb9f4a943a3f4
>
> --
> Now
Ingo,
Please pull the sched/0hz branch that can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/frederic/linux-dynticks.git
sched/0hz
HEAD: 9e932b2cc707209febd130978a5eb9f4a943a3f4
--
Now that scheduler_tick() has become resilient towards the absence of
ticks,
Ingo,
Please pull the sched/0hz branch that can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/frederic/linux-dynticks.git
sched/0hz
HEAD: 9e932b2cc707209febd130978a5eb9f4a943a3f4
--
Now that scheduler_tick() has become resilient towards the absence of
ticks,
28 matches
Mail list logo