From: Peter Zijlstra <peterz@infradead.org>
To: "Nikunj A. Dadhania" <nikunj@linux.vnet.ibm.com>
Cc: mingo@elte.hu, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sched: remove rcu_read_lock from wake_affine
Date: Tue, 07 Jun 2011 12:26:51 +0200 [thread overview]
Message-ID: <1307442411.2322.246.camel@twins> (raw)
In-Reply-To: <20110607101251.777.34547.stgit@IBM-009124035060.in.ibm.com>
On Tue, 2011-06-07 at 15:43 +0530, Nikunj A. Dadhania wrote:
> wake_affine is called from one path: select_task_rq_fair, which already has
> rcu read lock held.
>
> Signed-off-by: Nikunj A. Dadhania <nikunj@linux.vnet.ibm.com>
> ---
> kernel/sched_fair.c | 3 +--
> 1 files changed, 1 insertions(+), 2 deletions(-)
>
> diff --git a/kernel/sched_fair.c b/kernel/sched_fair.c
> index 354e26b..0bfec93 100644
> --- a/kernel/sched_fair.c
> +++ b/kernel/sched_fair.c
> @@ -1461,6 +1461,7 @@ static inline unsigned long effective_load(struct task_group *tg, int cpu,
>
> #endif
>
> +/* Assumes rcu_read_lock is held */
Not a big fan of such comments, esp with CONFIG_PROVE_RCU its better to
use those facilities, which is to say: if we're missing a
rcu_read_lock() the thing will yell bloody murder.
> static int wake_affine(struct sched_domain *sd, struct task_struct *p, int sync)
> {
> s64 this_load, load;
> @@ -1481,7 +1482,6 @@ static int wake_affine(struct sched_domain *sd, struct task_struct *p, int sync)
> * effect of the currently running task from the load
> * of the current CPU:
> */
> - rcu_read_lock();
> if (sync) {
> tg = task_group(current);
> weight = current->se.load.weight;
> @@ -1517,7 +1517,6 @@ static int wake_affine(struct sched_domain *sd, struct task_struct *p, int sync)
> balanced = this_eff_load <= prev_eff_load;
> } else
> balanced = true;
> - rcu_read_unlock();
>
> /*
> * If the currently running task will sleep within
>
OK, took the patch and removed the comment, thanks!
next prev parent reply other threads:[~2011-06-07 10:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-07 10:13 [PATCH] sched: remove rcu_read_lock from wake_affine Nikunj A. Dadhania
2011-06-07 10:26 ` Peter Zijlstra [this message]
2011-06-07 17:26 ` Paul E. McKenney
2011-06-07 17:29 ` Peter Zijlstra
2011-06-07 18:11 ` Paul E. McKenney
2011-07-01 15:16 ` [tip:sched/core] sched: Remove rcu_read_lock() from wake_affine() tip-bot for Nikunj A. Dadhania
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=1307442411.2322.246.camel@twins \
--to=peterz@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=nikunj@linux.vnet.ibm.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;
as well as URLs for NNTP newsgroup(s).