diff for duplicates of <20131217124656.GI21999@twins.programming.kicks-ass.net> diff --git a/a/1.txt b/N1/1.txt index e7dfbf2..fd7cec9 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -4,21 +4,21 @@ On Tue, Dec 17, 2013 at 04:02:58PM +0400, Kirill Tkhai wrote: > 13.12.2013, 19:42, "Peter Zijlstra" <peterz@infradead.org>: > > On Wed, Nov 27, 2013 at 07:59:13PM +0400, Kirill Tkhai wrote: > > -> >> This patch touches RT group scheduling case. +> >> �This patch touches RT group scheduling case. > >> -> >> Functions inc_rt_prio_smp() and dec_rt_prio_smp() change (global) rq's priority, -> >> while rt_rq passed to them may be not the top-level rt_rq. This is wrong, because -> >> changing of priority on a child level does not guarantee that the priority is -> >> the highest all over the rq. So, this leak makes RT balancing unusable. +> >> �Functions inc_rt_prio_smp() and dec_rt_prio_smp() change (global) rq's priority, +> >> �while rt_rq passed to them may be not the top-level rt_rq. This is wrong, because +> >> �changing of priority on a child level does not guarantee that the priority is +> >> �the highest all over the rq. So, this leak makes RT balancing unusable. > >> -> >> The short example: the task having the highest priority among all rq's RT tasks -> >> (no one other task has the same priority) are waking on a throttle rt_rq. -> >> The rq's cpupri is set to the task's priority equivalent, but real -> >> rq->rt.highest_prio.curr is less. +> >> �The short example: the task having the highest priority among all rq's RT tasks +> >> �(no one other task has the same priority) are waking on a throttle rt_rq. +> >> �The rq's cpupri is set to the task's priority equivalent, but real +> >> �rq->rt.highest_prio.curr is less. > >> -> >> The patch below fixes the problem. +> >> �The patch below fixes the problem. > >> -> >> It looks like all version have this bug, so I CC'ed stable mailing list. +> >> �It looks like all version have this bug, so I CC'ed stable mailing list. > > > > Yeah, I think this is right. > > diff --git a/a/content_digest b/N1/content_digest index b8e46d3..39ab472 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -17,21 +17,21 @@ "> 13.12.2013, 19:42, \"Peter Zijlstra\" <peterz@infradead.org>:\n" "> > On Wed, Nov 27, 2013 at 07:59:13PM +0400, Kirill Tkhai wrote:\n" "> >\n" - "> >> \302\240This patch touches RT group scheduling case.\n" + "> >> \303\257\302\277\302\275This patch touches RT group scheduling case.\n" "> >>\n" - "> >> \302\240Functions inc_rt_prio_smp() and dec_rt_prio_smp() change (global) rq's priority,\n" - "> >> \302\240while rt_rq passed to them may be not the top-level rt_rq. This is wrong, because\n" - "> >> \302\240changing of priority on a child level does not guarantee that the priority is\n" - "> >> \302\240the highest all over the rq. So, this leak makes RT balancing unusable.\n" + "> >> \303\257\302\277\302\275Functions inc_rt_prio_smp() and dec_rt_prio_smp() change (global) rq's priority,\n" + "> >> \303\257\302\277\302\275while rt_rq passed to them may be not the top-level rt_rq. This is wrong, because\n" + "> >> \303\257\302\277\302\275changing of priority on a child level does not guarantee that the priority is\n" + "> >> \303\257\302\277\302\275the highest all over the rq. So, this leak makes RT balancing unusable.\n" "> >>\n" - "> >> \302\240The short example: the task having the highest priority among all rq's RT tasks\n" - "> >> \302\240(no one other task has the same priority) are waking on a throttle rt_rq.\n" - "> >> \302\240The rq's cpupri is set to the task's priority equivalent, but real\n" - "> >> \302\240rq->rt.highest_prio.curr is less.\n" + "> >> \303\257\302\277\302\275The short example: the task having the highest priority among all rq's RT tasks\n" + "> >> \303\257\302\277\302\275(no one other task has the same priority) are waking on a throttle rt_rq.\n" + "> >> \303\257\302\277\302\275The rq's cpupri is set to the task's priority equivalent, but real\n" + "> >> \303\257\302\277\302\275rq->rt.highest_prio.curr is less.\n" "> >>\n" - "> >> \302\240The patch below fixes the problem.\n" + "> >> \303\257\302\277\302\275The patch below fixes the problem.\n" "> >>\n" - "> >> \302\240It looks like all version have this bug, so I CC'ed stable mailing list.\n" + "> >> \303\257\302\277\302\275It looks like all version have this bug, so I CC'ed stable mailing list.\n" "> >\n" "> > Yeah, I think this is right.\n" "> >\n" @@ -44,4 +44,4 @@ "\n" Thanks -517874a79d517c3c364b0bb94a6ddad46c5788fbe21edbf2b12f65e06a9f9cf8 +531cb53d3e1a4f8a38cc25aacba9c4c3c71c3cc5e51f5cffee410176c619391f
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.