Re: [BUG] Corrupted SCHED_DEADLINE bandwidth with cpusets

On 04/02/16 12:31, Steven Rostedt wrote: > On Thu, 4 Feb 2016 16:30:49 + > Juri Lelli wrote: > > > I've actually changed a bit this approach, and things seem better here. > > Could you please give this a try? (You can also fetch the same branch). > > It appears to fix the one issue I

Re: [BUG] Corrupted SCHED_DEADLINE bandwidth with cpusets

On Thu, 4 Feb 2016 16:30:49 + Juri Lelli wrote: > I've actually changed a bit this approach, and things seem better here. > Could you please give this a try? (You can also fetch the same branch). It appears to fix the one issue I pointed out, but it doesn't fix the issue with cpusets. #

Re: [BUG] Corrupted SCHED_DEADLINE bandwidth with cpusets

Hi Steve, On 04/02/16 12:27, Juri Lelli wrote: > On 04/02/16 12:04, Juri Lelli wrote: > > On 04/02/16 09:54, Juri Lelli wrote: > > > Hi Steve, > > > > > > first of all thanks a lot for your detailed report, if only all bug > > > reports were like this.. :) > > > > > > On 03/02/16 13:55, Steven

Re: [BUG] Corrupted SCHED_DEADLINE bandwidth with cpusets

On 04/02/16 12:04, Juri Lelli wrote: > On 04/02/16 09:54, Juri Lelli wrote: > > Hi Steve, > > > > first of all thanks a lot for your detailed report, if only all bug > > reports were like this.. :) > > > > On 03/02/16 13:55, Steven Rostedt wrote: > > [...] > > > > > Right. I think this is the

Re: [BUG] Corrupted SCHED_DEADLINE bandwidth with cpusets

On 04/02/16 09:54, Juri Lelli wrote: > Hi Steve, > > first of all thanks a lot for your detailed report, if only all bug > reports were like this.. :) > > On 03/02/16 13:55, Steven Rostedt wrote: [...] > > Right. I think this is the same thing that happens after hotplug. IIRC > the code paths

Re: [BUG] Corrupted SCHED_DEADLINE bandwidth with cpusets

Hi Steve, first of all thanks a lot for your detailed report, if only all bug reports were like this.. :) On 03/02/16 13:55, Steven Rostedt wrote: > There's an accounting issue with the SCHED_DEADLINE and the creation of > cpusets. If a SCHED_DEADLINE task already exists and a new root domain >

Re: [BUG] Corrupted SCHED_DEADLINE bandwidth with cpusets

Hi Steve, first of all thanks a lot for your detailed report, if only all bug reports were like this.. :) On 03/02/16 13:55, Steven Rostedt wrote: > There's an accounting issue with the SCHED_DEADLINE and the creation of > cpusets. If a SCHED_DEADLINE task already exists and a new root domain >

Re: [BUG] Corrupted SCHED_DEADLINE bandwidth with cpusets

On 04/02/16 12:04, Juri Lelli wrote: > On 04/02/16 09:54, Juri Lelli wrote: > > Hi Steve, > > > > first of all thanks a lot for your detailed report, if only all bug > > reports were like this.. :) > > > > On 03/02/16 13:55, Steven Rostedt wrote: > > [...] > > > > > Right. I think this is the

Re: [BUG] Corrupted SCHED_DEADLINE bandwidth with cpusets

On 04/02/16 09:54, Juri Lelli wrote: > Hi Steve, > > first of all thanks a lot for your detailed report, if only all bug > reports were like this.. :) > > On 03/02/16 13:55, Steven Rostedt wrote: [...] > > Right. I think this is the same thing that happens after hotplug. IIRC > the code paths

Re: [BUG] Corrupted SCHED_DEADLINE bandwidth with cpusets

Hi Steve, On 04/02/16 12:27, Juri Lelli wrote: > On 04/02/16 12:04, Juri Lelli wrote: > > On 04/02/16 09:54, Juri Lelli wrote: > > > Hi Steve, > > > > > > first of all thanks a lot for your detailed report, if only all bug > > > reports were like this.. :) > > > > > > On 03/02/16 13:55, Steven

Re: [BUG] Corrupted SCHED_DEADLINE bandwidth with cpusets

On Thu, 4 Feb 2016 16:30:49 + Juri Lelli wrote: > I've actually changed a bit this approach, and things seem better here. > Could you please give this a try? (You can also fetch the same branch). It appears to fix the one issue I pointed out, but it doesn't fix the issue

Re: [BUG] Corrupted SCHED_DEADLINE bandwidth with cpusets

On 04/02/16 12:31, Steven Rostedt wrote: > On Thu, 4 Feb 2016 16:30:49 + > Juri Lelli wrote: > > > I've actually changed a bit this approach, and things seem better here. > > Could you please give this a try? (You can also fetch the same branch). > > It appears to fix

Re: [BUG] Corrupted SCHED_DEADLINE bandwidth with cpusets

On Wed, 3 Feb 2016 13:55:50 -0500 Steven Rostedt wrote: > # grep dl /proc/sched_debug > dl_rq[0]: > .dl_nr_running : 0 > .dl_bw->bw : 996147 > .dl_bw->total_bw : -104857 > dl_rq[1]: > .dl_nr_running : 0 > .dl_bw->bw

[BUG] Corrupted SCHED_DEADLINE bandwidth with cpusets

There's an accounting issue with the SCHED_DEADLINE and the creation of cpusets. If a SCHED_DEADLINE task already exists and a new root domain is created, the calculation of the bandwidth among the root domains gets corrupted. For the reproducer, I downloaded Juri's tests:

[BUG] Corrupted SCHED_DEADLINE bandwidth with cpusets

There's an accounting issue with the SCHED_DEADLINE and the creation of cpusets. If a SCHED_DEADLINE task already exists and a new root domain is created, the calculation of the bandwidth among the root domains gets corrupted. For the reproducer, I downloaded Juri's tests:

Re: [BUG] Corrupted SCHED_DEADLINE bandwidth with cpusets

On Wed, 3 Feb 2016 13:55:50 -0500 Steven Rostedt wrote: > # grep dl /proc/sched_debug > dl_rq[0]: > .dl_nr_running : 0 > .dl_bw->bw : 996147 > .dl_bw->total_bw : -104857 > dl_rq[1]: > .dl_nr_running :