LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Cyrill Gorcunov <gorcunov@gmail.com>
Cc: Ingo Molnar <mingo@elte.hu>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: CFS related question
Date: Sat, 18 Oct 2008 22:28:18 +0200 [thread overview]
Message-ID: <1224361698.10548.38.camel@lappy.programming.kicks-ass.net> (raw)
In-Reply-To: <20081018200319.GC8188@localhost>
On Sun, 2008-10-19 at 00:03 +0400, Cyrill Gorcunov wrote:
> Hi Ingo, Peter,
>
> I just curious, look we have the following
>
> static struct sched_entity *pick_next_entity(struct cfs_rq *cfs_rq)
> {
> struct sched_entity *se = NULL;
>
> if (first_fair(cfs_rq)) {
> se = __pick_next_entity(cfs_rq);
> se = pick_next(cfs_rq, se);
> set_next_entity(cfs_rq, se);
> }
>
> return se;
> }
>
> which I presume may return NULL so the following piece
> could fail
>
> static struct task_struct *pick_next_task_fair(struct rq *rq)
> {
> struct task_struct *p;
> struct cfs_rq *cfs_rq = &rq->cfs;
> struct sched_entity *se;
>
> if (unlikely(!cfs_rq->nr_running))
> return NULL;
>
> do {
> --> se = pick_next_entity(cfs_rq);
> --> OOPs cfs_rq = group_cfs_rq(se);
> } while (cfs_rq);
>
> p = task_of(se);
> hrtick_start_fair(rq, p);
>
> return p;
> }
>
> Did I miss something? Or it comepletely can NOT happen?
pick_next_entity() only returns NULL when !first_fair(), which is when !
nr_running.
So the initial !nr_running check in pick_next_task_fair() will catch
that. Further nested RQs will never have !nr_running because then they
get dequeued.
next prev parent reply other threads:[~2008-10-18 20:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-18 20:03 Cyrill Gorcunov
2008-10-18 20:28 ` Peter Zijlstra [this message]
2008-10-19 5:29 ` Cyrill Gorcunov
2008-10-20 18:12 ` Hiroshi Shimamoto
2008-10-20 18:20 ` Cyrill Gorcunov
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=1224361698.10548.38.camel@lappy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=gorcunov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--subject='Re: CFS related question' \
/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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).