From: Jens Axboe <axboe@kernel.dk>
To: "jianchao.wang" <jianchao.w.wang@oracle.com>,
Anchal Agarwal <anchalag@amzn.com>
Cc: fllinden@amazon.com,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] blk-wbt: get back the missed wakeup from __wbt_done
Date: Mon, 27 Aug 2018 09:37:47 -0600 [thread overview]
Message-ID: <cc7b19f7-b5c5-e89d-eb12-cdff6e35fb4d@kernel.dk> (raw)
In-Reply-To: <00445460-d826-4d85-c5f4-fa565892da01@oracle.com>
On 8/26/18 9:52 PM, jianchao.wang wrote:
> Hi Jens
>
> On 08/25/2018 11:41 PM, Jens Axboe wrote:
>> do {
>> - set_current_state(TASK_UNINTERRUPTIBLE);
>> + if (test_bit(0, &data.flags))
>> + break;
>>
>> - if (!has_sleeper && rq_wait_inc_below(rqw, get_limit(rwb, rw)))
>> + WARN_ON_ONCE(list_empty(&data.wq.entry));
>> +
>> + if (!has_sleeper &&
>> + rq_wait_inc_below(rqw, get_limit(rwb, rw))) {
>> + finish_wait(&rqw->wait, &data.wq);
>> +
>> + /*
>> + * We raced with wbt_wake_function() getting a token,
>> + * which means we now have two. Put ours and wake
>> + * anyone else potentially waiting for one.
>> + */
>> + if (test_bit(0, &data.flags))
>> + wbt_rqw_done(rwb, rqw, wb_acct);
>> break;
>
> Just use 'bool' variable should be OK
> After finish_wait, no one could race with us here.
I was mostly concerned with the check post prep_to_wait(), but since the
spin unlock should include a barrier, the bool should actually be enough.
I'll change that back once I test.
--
Jens Axboe
next prev parent reply other threads:[~2018-08-27 15:37 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-23 13:08 [PATCH] blk-wbt: get back the missed wakeup from __wbt_done Jianchao Wang
2018-08-23 15:37 ` Jens Axboe
2018-08-23 16:24 ` van der Linden, Frank
[not found] ` <20180823210144.GB5624@kaos-source-ops-60001.pdx1.amazon.com>
2018-08-23 23:03 ` Jens Axboe
2018-08-23 23:14 ` Jens Axboe
2018-08-24 5:55 ` jianchao.wang
2018-08-24 16:40 ` van der Linden, Frank
2018-08-24 16:44 ` Jens Axboe
[not found] ` <20180824181223.GA9049@kaos-source-ops-60001.pdx1.amazon.com>
2018-08-24 18:50 ` Jens Axboe
[not found] ` <20180824203305.GA4690@kaos-source-ops-60001.pdx1.amazon.com>
2018-08-24 20:41 ` Jens Axboe
2018-08-25 15:41 ` Jens Axboe
2018-08-27 3:52 ` jianchao.wang
2018-08-27 6:15 ` jianchao.wang
2018-08-27 14:51 ` Jens Axboe
2018-08-28 2:52 ` jianchao.wang
2018-08-27 15:37 ` Jens Axboe [this message]
2018-08-23 15:42 ` Jens Axboe
2018-08-24 2:06 ` jianchao.wang
2018-08-24 14:40 ` Jens Axboe
2018-08-24 14:58 ` Jens Axboe
2018-08-24 17:14 ` Eduardo Valentin
2018-08-24 17:17 ` 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=cc7b19f7-b5c5-e89d-eb12-cdff6e35fb4d@kernel.dk \
--to=axboe@kernel.dk \
--cc=anchalag@amzn.com \
--cc=fllinden@amazon.com \
--cc=jianchao.w.wang@oracle.com \
--cc=linux-block@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;
as well as URLs for NNTP newsgroup(s).