On 09/03/2014 12:00 PM, Daniel Wagner wrote: > > On 09/02/2014 04:16 PM, Vincent Legout wrote: >> Hi, >> >> Juri Lelli <juri.lelli@xxxxxxxxx> writes: >> >>> thanks a lot for your report. I was also actually experiencing something that I >>> think is related to your issue, but then I didn't find any time to send out >>> a proper patch :/. >>> >>> Could you please test what I've attached and see if it fixes your problem? >> >> Thanks for the patch, it fixes the second issue I mentioned in my >> previous email, i.e. the one for which I posted a patch. For this issue, >> FWIW: >> >> Tested-by: Vincent Legout <vincent@xxxxxxxxxxx> >> Tested-by: Kevin Burns <kevinpb@xxxxxx> >> >> But it doesn't seem to fix the main issue related to cpusets and >> SCHED_DEADLINE. It still fails if we don't come back to SCHED_OTHER >> before moving the task to another cpuset. I think it's due to the fact >> that SCHED_DEADLINE's data structures don't seem to be aware that a task >> migrated, they are not updated during this process. Any idea where I >> could have a look? Or if this is not supported, would it be possible to >> add some checks such that total_bw doesn't overflow when calling >> __dl_clear? If yes, I can try to provide a patch. > > I just saw this thread after sending a patch for this problem. It's not > yet in the archive, though it is called: > > "[PATCH] sched: Reset bandwith on task when switching from > SCHED_DEADLINE away" > > And obviously, I forgot to cc Juri. Sorry about that. After fixing my sender address it even hit the archive: https://lkml.org/lkml/2014/9/3/354 cheers, daniel -- To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
