public inbox for linux-block@vger.kernel.org
 help / color / mirror / Atom feed
From: Jan Kara <jack@suse.cz>
To: Gabriel Krisman Bertazi <krisman@suse.de>
Cc: axboe@kernel.dk, mingo@redhat.com, peterz@infradead.org,
	jack@suse.cz, linux-kernel@vger.kernel.org,
	linux-block@vger.kernel.org, liusong@linux.alibaba.com,
	chaitanyak@nvidia.com
Subject: Re: [PATCH 2/3] wait: Return number of exclusive waiters awaken
Date: Wed, 16 Nov 2022 12:06:03 +0100	[thread overview]
Message-ID: <20221116110603.6rndj2eei6mi6k33@quack3> (raw)
In-Reply-To: <20221115224553.23594-3-krisman@suse.de>

On Tue 15-11-22 17:45:52, Gabriel Krisman Bertazi wrote:
> Sbitmap code will need to know how many waiters were actually woken for
> its batched wakeups implementation.  Return the number of woken
> exclusive waiters from __wake_up() to facilitate that.
> 
> Suggested-by: Jan Kara <jack@suse.cz>
> Signed-off-by: Gabriel Krisman Bertazi <krisman@suse.de>

Looks good. Feel free to add:

Reviewed-by: Jan Kara <jack@suse.cz>

								Honza

> ---
>  include/linux/wait.h |  2 +-
>  kernel/sched/wait.c  | 18 +++++++++++-------
>  2 files changed, 12 insertions(+), 8 deletions(-)
> 
> diff --git a/include/linux/wait.h b/include/linux/wait.h
> index 7f5a51aae0a7..a0307b516b09 100644
> --- a/include/linux/wait.h
> +++ b/include/linux/wait.h
> @@ -209,7 +209,7 @@ __remove_wait_queue(struct wait_queue_head *wq_head, struct wait_queue_entry *wq
>  	list_del(&wq_entry->entry);
>  }
>  
> -void __wake_up(struct wait_queue_head *wq_head, unsigned int mode, int nr, void *key);
> +int __wake_up(struct wait_queue_head *wq_head, unsigned int mode, int nr, void *key);
>  void __wake_up_locked_key(struct wait_queue_head *wq_head, unsigned int mode, void *key);
>  void __wake_up_locked_key_bookmark(struct wait_queue_head *wq_head,
>  		unsigned int mode, void *key, wait_queue_entry_t *bookmark);
> diff --git a/kernel/sched/wait.c b/kernel/sched/wait.c
> index 9860bb9a847c..133b74730738 100644
> --- a/kernel/sched/wait.c
> +++ b/kernel/sched/wait.c
> @@ -121,11 +121,12 @@ static int __wake_up_common(struct wait_queue_head *wq_head, unsigned int mode,
>  	return nr_exclusive;
>  }
>  
> -static void __wake_up_common_lock(struct wait_queue_head *wq_head, unsigned int mode,
> +static int __wake_up_common_lock(struct wait_queue_head *wq_head, unsigned int mode,
>  			int nr_exclusive, int wake_flags, void *key)
>  {
>  	unsigned long flags;
>  	wait_queue_entry_t bookmark;
> +	int remaining = nr_exclusive;
>  
>  	bookmark.flags = 0;
>  	bookmark.private = NULL;
> @@ -134,10 +135,12 @@ static void __wake_up_common_lock(struct wait_queue_head *wq_head, unsigned int
>  
>  	do {
>  		spin_lock_irqsave(&wq_head->lock, flags);
> -		nr_exclusive = __wake_up_common(wq_head, mode, nr_exclusive,
> +		remaining = __wake_up_common(wq_head, mode, remaining,
>  						wake_flags, key, &bookmark);
>  		spin_unlock_irqrestore(&wq_head->lock, flags);
>  	} while (bookmark.flags & WQ_FLAG_BOOKMARK);
> +
> +	return nr_exclusive - remaining;
>  }
>  
>  /**
> @@ -147,13 +150,14 @@ static void __wake_up_common_lock(struct wait_queue_head *wq_head, unsigned int
>   * @nr_exclusive: how many wake-one or wake-many threads to wake up
>   * @key: is directly passed to the wakeup function
>   *
> - * If this function wakes up a task, it executes a full memory barrier before
> - * accessing the task state.
> + * If this function wakes up a task, it executes a full memory barrier
> + * before accessing the task state.  Returns the number of exclusive
> + * tasks that were awaken.
>   */
> -void __wake_up(struct wait_queue_head *wq_head, unsigned int mode,
> -			int nr_exclusive, void *key)
> +int __wake_up(struct wait_queue_head *wq_head, unsigned int mode,
> +	      int nr_exclusive, void *key)
>  {
> -	__wake_up_common_lock(wq_head, mode, nr_exclusive, 0, key);
> +	return __wake_up_common_lock(wq_head, mode, nr_exclusive, 0, key);
>  }
>  EXPORT_SYMBOL(__wake_up);
>  
> -- 
> 2.35.3
> 
-- 
Jan Kara <jack@suse.com>
SUSE Labs, CR

  reply	other threads:[~2022-11-16 11:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-15 22:45 [PATCH 0/3] sbitmap: Fix two issues in the per-bitmap wakeup counter code Gabriel Krisman Bertazi
2022-11-15 22:45 ` [PATCH 1/3] sbitmap: Advance the queue index before waking up a queue Gabriel Krisman Bertazi
2022-11-15 22:45 ` [PATCH 2/3] wait: Return number of exclusive waiters awaken Gabriel Krisman Bertazi
2022-11-16 11:06   ` Jan Kara [this message]
2022-11-16 20:22   ` Peter Zijlstra
2022-11-15 22:45 ` [PATCH 3/3] sbitmap: Try each queue to wake up at least one waiter Gabriel Krisman Bertazi
2022-11-16 11:09   ` Jan Kara
2022-11-16 18:49 ` [PATCH 0/3] sbitmap: Fix two issues in the per-bitmap wakeup counter code Jens Axboe

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=20221116110603.6rndj2eei6mi6k33@quack3 \
    --to=jack@suse.cz \
    --cc=axboe@kernel.dk \
    --cc=chaitanyak@nvidia.com \
    --cc=krisman@suse.de \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=liusong@linux.alibaba.com \
    --cc=mingo@redhat.com \
    --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