On Wed, Mar 23, 2016 at 05:50:14AM +0100, Mike Galbraith wrote:
> (cc)
>
> On Tue, 2016-03-22 at 16:22 -0400, Ion Badulescu wrote:
> > On 03/17/2016 10:28 PM, Mike Galbraith wrote:
> > > On Wed, 2016-03-16 at 12:15 -0400, Ion Badulescu wrote:
> > > > Just following up to my own email:
> > > >
>
On Wed, Mar 23, 2016 at 05:50:14AM +0100, Mike Galbraith wrote:
> (cc)
>
> On Tue, 2016-03-22 at 16:22 -0400, Ion Badulescu wrote:
> > On 03/17/2016 10:28 PM, Mike Galbraith wrote:
> > > On Wed, 2016-03-16 at 12:15 -0400, Ion Badulescu wrote:
> > > > Just following up to my own email:
> > > >
>
(cc)
On Tue, 2016-03-22 at 16:22 -0400, Ion Badulescu wrote:
> On 03/17/2016 10:28 PM, Mike Galbraith wrote:
> > On Wed, 2016-03-16 at 12:15 -0400, Ion Badulescu wrote:
> > > Just following up to my own email:
> > >
> > > It turns out that we can eliminate the RCU stalls by changing from
> > >
(cc)
On Tue, 2016-03-22 at 16:22 -0400, Ion Badulescu wrote:
> On 03/17/2016 10:28 PM, Mike Galbraith wrote:
> > On Wed, 2016-03-16 at 12:15 -0400, Ion Badulescu wrote:
> > > Just following up to my own email:
> > >
> > > It turns out that we can eliminate the RCU stalls by changing from
> > >
On 03/17/2016 10:28 PM, Mike Galbraith wrote:
On Wed, 2016-03-16 at 12:15 -0400, Ion Badulescu wrote:
Just following up to my own email:
It turns out that we can eliminate the RCU stalls by changing from
CONFIG_RCU_NOCB_CPU_ALL to CONFIG_RCU_NOCB_CPU_NONE. Letting each cpu
handle its own RCU
On 03/17/2016 10:28 PM, Mike Galbraith wrote:
On Wed, 2016-03-16 at 12:15 -0400, Ion Badulescu wrote:
Just following up to my own email:
It turns out that we can eliminate the RCU stalls by changing from
CONFIG_RCU_NOCB_CPU_ALL to CONFIG_RCU_NOCB_CPU_NONE. Letting each cpu
handle its own RCU
Just following up to my own email:
It turns out that we can eliminate the RCU stalls by changing from
CONFIG_RCU_NOCB_CPU_ALL to CONFIG_RCU_NOCB_CPU_NONE. Letting each cpu
handle its own RCU callbacks completely fixes the problems for us.
Now, CONFIG_NO_HZ_FULL and CONFIG_RCU_NOCB_CPU_ALL is
Just following up to my own email:
It turns out that we can eliminate the RCU stalls by changing from
CONFIG_RCU_NOCB_CPU_ALL to CONFIG_RCU_NOCB_CPU_NONE. Letting each cpu
handle its own RCU callbacks completely fixes the problems for us.
Now, CONFIG_NO_HZ_FULL and CONFIG_RCU_NOCB_CPU_ALL is
On Wed, 2016-03-16 at 12:15 -0400, Ion Badulescu wrote:
> Just following up to my own email:
>
> It turns out that we can eliminate the RCU stalls by changing from
> CONFIG_RCU_NOCB_CPU_ALL to CONFIG_RCU_NOCB_CPU_NONE. Letting each cpu
> handle its own RCU callbacks completely fixes the
On Wed, 2016-03-16 at 12:15 -0400, Ion Badulescu wrote:
> Just following up to my own email:
>
> It turns out that we can eliminate the RCU stalls by changing from
> CONFIG_RCU_NOCB_CPU_ALL to CONFIG_RCU_NOCB_CPU_NONE. Letting each cpu
> handle its own RCU callbacks completely fixes the
Hello,
We run a compute cluster of about 800 or so machines here, which makes
heavy use of NFS and fscache (on a dedicated local drive with an ext4
filesystem) and also exercises the other local drives pretty hard. All
the compute jobs run as unprivileged users with SCHED_OTHER scheduling,
nice
Hello,
We run a compute cluster of about 800 or so machines here, which makes
heavy use of NFS and fscache (on a dedicated local drive with an ext4
filesystem) and also exercises the other local drives pretty hard. All
the compute jobs run as unprivileged users with SCHED_OTHER scheduling,
nice
12 matches
Mail list logo