mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jacob Wen <jian.w.wen@oracle.com>
To: linux-fsdevel@vger.kernel.org,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	linux-block@vger.kernel.org
Subject: Re: [PATCH 1/2] block: use DEFINE_WAIT_BIT instead of DEFINE_WAIT for bit wait queue
Date: Fri, 21 Aug 2020 09:32:10 +0800	[thread overview]
Message-ID: <3eff2c13-640e-6686-9a79-70c97e9fdfa5@oracle.com> (raw)
In-Reply-To: <20200813050552.26856-1-jian.w.wen@oracle.com>

Can I have a review?

On 8/13/20 1:05 PM, Jacob Wen wrote:
> DEFINE_WAIT_BIT uses wake_bit_function() which is able to avoid
> false-wakeups due to possible hash collisions in the bit wait table.
>
> Signed-off-by: Jacob Wen <jian.w.wen@oracle.com>
> ---
>   fs/block_dev.c | 6 +++---
>   1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/fs/block_dev.c b/fs/block_dev.c
> index 0ae656e022fd..ba4fad08cdaf 100644
> --- a/fs/block_dev.c
> +++ b/fs/block_dev.c
> @@ -1062,12 +1062,12 @@ static int bd_prepare_to_claim(struct block_device *bdev,
>   	/* if claiming is already in progress, wait for it to finish */
>   	if (whole->bd_claiming) {
>   		wait_queue_head_t *wq = bit_waitqueue(&whole->bd_claiming, 0);
> -		DEFINE_WAIT(wait);
> +		DEFINE_WAIT_BIT(wait, &whole->bd_claiming, 0);
>   
> -		prepare_to_wait(wq, &wait, TASK_UNINTERRUPTIBLE);
> +		prepare_to_wait(wq, &wait.wq_entry, TASK_UNINTERRUPTIBLE);
>   		spin_unlock(&bdev_lock);
>   		schedule();
> -		finish_wait(wq, &wait);
> +		finish_wait(wq, &wait.wq_entry);
>   		spin_lock(&bdev_lock);
>   		goto retry;
>   	}

       reply	other threads:[~2020-08-21  1:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20200813050552.26856-1-jian.w.wen@oracle.com>
2020-08-21  1:32 ` Jacob Wen [this message]
     [not found] ` <20200813050552.26856-2-jian.w.wen@oracle.com>
2020-08-21  1:33   ` [PATCH 2/2] writeback: " Jacob Wen

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=3eff2c13-640e-6686-9a79-70c97e9fdfa5@oracle.com \
    --to=jian.w.wen@oracle.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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®