mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Byungchul Park <byungchul.park@lge.com>
To: <peterz@infradead.org>, <mingo@kernel.org>
Cc: <linux-kernel@vger.kernel.org>, <kernel-team@lge.com>
Subject: Re: [PATCH] sched: Wake up all non-exclusive waiters in __wake_up_common()
Date: Fri, 10 Mar 2017 16:00:27 +0900	[thread overview]
Message-ID: <20170310070026.GF11100@X58A-UD3R> (raw)
In-Reply-To: <1488932512-18999-1-git-send-email-byungchul.park@lge.com>

On Wed, Mar 08, 2017 at 09:21:52AM +0900, Byungchul Park wrote:
> __wake_up_common() should wake up all non-exclusive waiters and
> exclusive waiters as many as nr_exclusive, but currently it does not.
> 
> Consider a wait queue like the following for example:
> 
>    A(exclusive) -> B(non-exclusive) -> C(non-exclusive)
> 
> Current code will wake up only A when nr_exclusive = 1, but has to wake
> up A, B and C. Make it do as we expect.

I'm wondering if I was wrong. Am I wrong?

> 
> Signed-off-by: Byungchul Park <byungchul.park@lge.com>
> ---
>  kernel/sched/wait.c | 15 +++++++++++++--
>  1 file changed, 13 insertions(+), 2 deletions(-)
> 
> diff --git a/kernel/sched/wait.c b/kernel/sched/wait.c
> index 9453efe..0ea1083 100644
> --- a/kernel/sched/wait.c
> +++ b/kernel/sched/wait.c
> @@ -67,12 +67,23 @@ static void __wake_up_common(wait_queue_head_t *q, unsigned int mode,
>  {
>  	wait_queue_t *curr, *next;
>  
> +	/*
> +	 * We use nr_exclusive = 0 to wake up all no matter whether
> +	 * WQ_FLAG_EXCLUSIVE is set. However, we have to distinguish
> +	 * between the case and having finished all exclusive wake-up.
> +	 * So make nr_exclusive non-zero in advance in the former case.
> +	 */
> +	nr_exclusive = nr_exclusive ?: -1;
> +
>  	list_for_each_entry_safe(curr, next, &q->task_list, task_list) {
>  		unsigned flags = curr->flags;
>  
> +		if ((flags & WQ_FLAG_EXCLUSIVE) && !nr_exclusive)
> +			continue;
> +
>  		if (curr->func(curr, mode, wake_flags, key) &&
> -				(flags & WQ_FLAG_EXCLUSIVE) && !--nr_exclusive)
> -			break;
> +		    (flags & WQ_FLAG_EXCLUSIVE))
> +			nr_exclusive--;
>  	}
>  }
>  
> -- 
> 1.9.1

  reply	other threads:[~2017-03-10  7:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-08  0:21 Byungchul Park
2017-03-10  7:00 ` Byungchul Park [this message]
2017-03-20 10:41 ` Peter Zijlstra
2017-03-20 23:13   ` Byungchul Park

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=20170310070026.GF11100@X58A-UD3R \
    --to=byungchul.park@lge.com \
    --cc=kernel-team@lge.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.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

all inboxes | Powered by JetHome®