Re: [RFC][PATCH 3/4] sched: Change sched_class::set_cpus_allowed calling context

2015-05-18 Thread Peter Zijlstra
On Mon, May 18, 2015 at 03:37:43PM +0800, pang.xun...@zte.com.cn wrote: Hi Peter, With this modification, I think the pushing action in my previous patch Check to push the task away after its affinity was changed will not be able to be implemented inside sched_class::set_cpus_allowed().

Re: [RFC][PATCH 3/4] sched: Change sched_class::set_cpus_allowed calling context

2015-05-18 Thread Peter Zijlstra
On Mon, May 18, 2015 at 10:32:16AM +0200, Peter Zijlstra wrote: On Mon, May 18, 2015 at 03:37:43PM +0800, pang.xun...@zte.com.cn wrote: Hi Peter, With this modification, I think the pushing action in my previous patch Check to push the task away after its affinity was changed will not

Re: [RFC][PATCH 3/4] sched: Change sched_class::set_cpus_allowed calling context

2015-05-18 Thread Juri Lelli
Hi Peter, On 05/18/2015 09:32 AM, Peter Zijlstra wrote: On Mon, May 18, 2015 at 03:37:43PM +0800, pang.xun...@zte.com.cn wrote: Hi Peter, With this modification, I think the pushing action in my previous patch Check to push the task away after its affinity was changed will not be able to

[RFC][PATCH 3/4] sched: Change sched_class::set_cpus_allowed calling context

2015-05-15 Thread Peter Zijlstra
Change the calling context of sched_class::set_cpus_allowed() such that we can assume the task is inactive. This allows us to easily make changes that affect accounting done by enqueue/dequeue. This does in fact completely remove set_cpus_allowed_rt and greatly reduces set_cpus_allowed_dl.