mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Paul Turner <pjt@google.com>
Cc: Max Hailperin <max@gustavus.edu>,
	LKML <linux-kernel@vger.kernel.org>,
	Ingo Molnar <mingo@kernel.org>
Subject: Re: PROBLEM: Persistent unfair sharing of a processor by auto groups in 3.11-rc2 (has twice regressed)
Date: Fri, 26 Jul 2013 23:03:17 +0200	[thread overview]
Message-ID: <20130726210317.GC20909@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <CAPM31RJ7Xh5A9cTT_-qd47RH3pRhCqiuh-uKx1gktDk0g-5NNg@mail.gmail.com>



OK, so I have the below; however on a second look, Paul, shouldn't that
update_cfs_shares() call be in entity_tick(), right after calling
update_cfs_rq_blocked_load(). Because placing it in
update_cfs_rq_blocked_load() means its now called twice on the
enqueue/dequeue paths through:

  {en,de}queue_entity()
    {en,de}queue_entity_load_avg()
      update_cfs_rq_blocked_load()
        update_cfs_shares()



---
Subject: sched: Ensure update_cfs_shares() is called for parents of continuously-running tasks
From: Max Hailperin <max@gustavus.edu>

We typically update a task_group's shares within the dequeue/enqueue
path.  However, continuously running tasks sharing a CPU are not
subject to these updates as they are only put/picked.  Unfortunately,
when we reverted f269ae046 (in 17bc14b7), we lost the augmenting
periodic update that was supposed to account for this; resulting in a
potential loss of fairness.

To fix this, re-introduce the explicit update in
update_cfs_rq_blocked_load() [called via entity_tick()].

Cc: stable@kernel.org
Reviewed-by: Paul Turner <pjt@google.com>
Signed-off-by: Peter Zijlstra <peterz@infradead.org>
---
 kernel/sched/fair.c |    1 +
 1 file changed, 1 insertion(+)

--- a/kernel/sched/fair.c
+++ b/kernel/sched/fair.c
@@ -1531,6 +1531,7 @@ static void update_cfs_rq_blocked_load(s
 	}
 
 	__update_cfs_rq_tg_load_contrib(cfs_rq, force_update);
+	update_cfs_shares(cfs_rq);
 }
 
 static inline void update_rq_runnable_avg(struct rq *rq, int runnable)

  reply	other threads:[~2013-07-26 21:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <9E84D12D-7389-4D9A-803A-91FD704A92FA@gustavus.edu>
     [not found] ` <20130725112123.GT27075@twins.programming.kicks-ass.net>
     [not found]   ` <228E8D34-E1A9-4D82-B353-F095E473B8D7@gustavus.edu>
     [not found]     ` <20130725164051.GZ27075@twins.programming.kicks-ass.net>
     [not found]       ` <20130725211521.GE18254@gmail.com>
2013-07-26 12:27         ` Paul Turner
2013-07-26 12:43           ` Paul Turner
2013-07-26 21:03             ` Peter Zijlstra [this message]
2013-07-26 21:24               ` Paul Turner
2013-07-26 21:50                 ` Peter Zijlstra
2013-07-27  1:08                   ` Paul Turner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20130726210317.GC20909@twins.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=max@gustavus.edu \
    --cc=mingo@kernel.org \
    --cc=pjt@google.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome