From: Pavel Begunkov <[email protected]>
To: Hao Xu <[email protected]>, Jens Axboe <[email protected]>
Cc: [email protected], Joseph Qi <[email protected]>
Subject: Re: [PATCH] io-wq: simplify code in __io_worker_busy
Date: Fri, 2 Apr 2021 11:38:55 +0100 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On 02/04/2021 11:18, Hao Xu wrote:
> leverage xor to simplify code in __io_worker_busy
I don't like hard-coded ^1 because if indexes change it may break.
One option is to leave it to the compiler:
idx = bound : WQ_BOUND ? WQ_UNBOUND;
compl_idx = bound : WQ_UNBOUND ? WQ_BOUND;
Or add a BUILD_BUG_ON() checking that WQ_BOUND and WQ_UNBOUND
are mod 2 complementary.
>
> Signed-off-by: Hao Xu <[email protected]>
> ---
> fs/io-wq.c | 13 ++++---------
> 1 file changed, 4 insertions(+), 9 deletions(-)
>
> diff --git a/fs/io-wq.c b/fs/io-wq.c
> index 7434eb40ca8c..f77e4704d7c7 100644
> --- a/fs/io-wq.c
> +++ b/fs/io-wq.c
> @@ -292,16 +292,11 @@ static void __io_worker_busy(struct io_wqe *wqe, struct io_worker *worker,
> worker_bound = (worker->flags & IO_WORKER_F_BOUND) != 0;
> work_bound = (work->flags & IO_WQ_WORK_UNBOUND) == 0;
> if (worker_bound != work_bound) {
> + int index = work_bound ? IO_WQ_ACCT_UNBOUND : IO_WQ_ACCT_BOUND;
> io_wqe_dec_running(worker);
> - if (work_bound) {
> - worker->flags |= IO_WORKER_F_BOUND;
> - wqe->acct[IO_WQ_ACCT_UNBOUND].nr_workers--;
> - wqe->acct[IO_WQ_ACCT_BOUND].nr_workers++;
> - } else {
> - worker->flags &= ~IO_WORKER_F_BOUND;
> - wqe->acct[IO_WQ_ACCT_UNBOUND].nr_workers++;
> - wqe->acct[IO_WQ_ACCT_BOUND].nr_workers--;
> - }
> + worker->flags ^= IO_WORKER_F_BOUND;
> + wqe->acct[index].nr_workers--;
> + wqe->acct[index^1].nr_workers++;
> io_wqe_inc_running(worker);
> }
> }
>
--
Pavel Begunkov
next prev parent reply other threads:[~2021-04-02 10:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-02 10:18 [PATCH] io-wq: simplify code in __io_worker_busy Hao Xu
2021-04-02 10:38 ` Pavel Begunkov [this message]
2021-04-04 19:17 ` Jens Axboe
2021-04-05 7:53 ` [PATCH v3] " Hao Xu
2021-04-05 21:46 ` Jens Axboe
2021-04-06 2:18 ` Hao Xu
2021-04-06 3:08 ` [PATCH v4] " Hao Xu
2021-04-06 15:36 ` Jens Axboe
2021-04-07 18:28 ` Pavel Begunkov
2021-04-05 7:36 ` [PATCH v2] " Hao Xu
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 \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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