public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Juri Lelli <juri.lelli@gmail.com>
To: Peter Zijlstra <peterz@infradead.org>,
	Steven Rostedt <rostedt@goodmis.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Ingo Molnar <mingo@kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH v3] sched/deadline: Fix bad accounting of nr_running
Date: Wed, 19 Feb 2014 11:32:41 +0100	[thread overview]
Message-ID: <53048849.3000601@gmail.com> (raw)
In-Reply-To: <20140219084618.GF27965@twins.programming.kicks-ass.net>

On 02/19/2014 09:46 AM, Peter Zijlstra wrote:
> On Tue, Feb 18, 2014 at 09:50:12PM -0500, Steven Rostedt wrote:
>>  
>>> Rationale for this odd behavior is that, when a task is throttled, it
>>> is removed only from the dl_rq, but we keep it on_rq (as this is not
>>> a "full dequeue", that is the task is not actually sleeping). But, it
>>> is also true that, while throttled a task behaves like it is sleeping
>>> (e.g., its timer will fire on a new CPU if the old one is dead). So,
>>> Steven's fix sounds also semantically correct.
>>
>> Actually, it seems that I was hitting it again, but this time getting a
>> negative number. OK, after looking at the code a bit more, I think we
>> should update the runqueue nr_running only when the task is officially
>> enqueued and dequeued, and all accounting within, will not touch that
>> number.

This is a different way to get the same result (mildly tested on my box):

---
 kernel/sched/deadline.c |    3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/kernel/sched/deadline.c b/kernel/sched/deadline.c
index 0dd5e09..675dad3 100644
--- a/kernel/sched/deadline.c
+++ b/kernel/sched/deadline.c
@@ -837,7 +837,8 @@ static void enqueue_task_dl(struct rq *rq, struct task_struct *p, int flags)
        if (!task_current(rq, p) && p->nr_cpus_allowed > 1)
                enqueue_pushable_dl_task(rq, p);

-       inc_nr_running(rq);
+       if (!(flags & ENQUEUE_REPLENISH))
+               inc_nr_running(rq);
 }

 static void __dequeue_task_dl(struct rq *rq, struct task_struct *p, int flags)
--

We touch nr_running only when we don't enqueue back as a consequence
of a replenishment.

> 
> But if the task is throttled it should still very much decrement the
> number. There's places that very much rely on nr_running be exactly the
> number of runnable tasks.
> 

This is a different thing, and V2 seemed to implement this behavior
(that's why I said it looked semantically correct).

Thanks,

- Juri

  reply	other threads:[~2014-02-19 10:32 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-15  4:59 [PATCH] sched/deadline: Fix bad accounting of nr_running Steven Rostedt
2014-02-15  9:52 ` Peter Zijlstra
2014-02-15 13:03   ` Steven Rostedt
2014-02-15 13:08   ` [PATCH v2] " Steven Rostedt
2014-02-17 15:47 ` [PATCH] " Juri Lelli
2014-02-19  2:50   ` [PATCH v3] " Steven Rostedt
2014-02-19  8:46     ` Peter Zijlstra
2014-02-19 10:32       ` Juri Lelli [this message]
2014-02-19 13:14         ` Juri Lelli
2014-02-19 17:45           ` Steven Rostedt

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=53048849.3000601@gmail.com \
    --to=juri.lelli@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    /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