From: Jens Axboe <axboe@kernel.dk>
To: Christoph Hellwig <hch@lst.de>
Cc: linux-block@vger.kernel.org, linux-xfs@vger.kernel.org,
dchinner@redhat.com
Subject: Re: [PATCH 3/3] blk-wbt: throttle discards like background writes
Date: Mon, 7 May 2018 09:51:03 -0600 [thread overview]
Message-ID: <d2657561-8c24-9a29-6aa1-01e6548a0d31@kernel.dk> (raw)
In-Reply-To: <20180507095746.GC25210@lst.de>
On 5/7/18 3:57 AM, Christoph Hellwig wrote:
>> -static inline struct rq_wait *get_rq_wait(struct rq_wb *rwb, bool is_kswapd)
>> +static inline struct rq_wait *get_rq_wait(struct rq_wb *rwb, bool is_trim,
>> + bool is_kswapd)
>> {
>> - return &rwb->rq_wait[is_kswapd];
>> + if (is_trim)
>> + return &rwb->rq_wait[WBT_REQ_DISCARD];
>> + else if (is_kswapd)
>> + return &rwb->rq_wait[WBT_REQ_KSWAPD];
>> + else
>> + return &rwb->rq_wait[WBT_REQ_BG];
>> }
>
> Wouldn't it be more useful to pass a enum wbt_flag here?
>
> Or just have a wbt_flag_to_wait_idx helper and do the array indexing
> in the callers?
It would be cleaner, but we don't have wbt_flag everywhere we need it.
Though I guess we could swap the masking in wbt_wait() and do it
before the __wbt_wait() call, and just use that. Since we only do
the indexing in that one spot, I don't think we should add a helper.
>
>> {
>> const int op = bio_op(bio);
>>
>> - /*
>> - * If not a WRITE, do nothing
>> - */
>> - if (op != REQ_OP_WRITE)
>> - return false;
>> + if (op == REQ_OP_WRITE) {
>> + /*
>> + * Don't throttle WRITE_ODIRECT
>> + */
>> + if ((bio->bi_opf & (REQ_SYNC | REQ_IDLE)) ==
>> + (REQ_SYNC | REQ_IDLE))
>> + return false;
>>
>> - /*
>> - * Don't throttle WRITE_ODIRECT
>> - */
>> - if ((bio->bi_opf & (REQ_SYNC | REQ_IDLE)) == (REQ_SYNC | REQ_IDLE))
>> - return false;
>> + return true;
>> + } else if (op == REQ_OP_DISCARD)
>> + return true;
>
> what about:
>
> switch (bio_op(bio)) {
> case REQ_OP_WRITE:
> /*
> * Don't throttle WRITE_ODIRECT
> */
> if ((bio->bi_opf & (REQ_SYNC | REQ_IDLE)) ==
> (REQ_SYNC | REQ_IDLE))
> return false;
> /*FALLTHROUGH*/
> case REQ_OP_DISCARD:
> return true;
> default:
> return false;
Sure, I can do that. I'll spin a v2.
--
Jens Axboe
next prev parent reply other threads:[~2018-05-07 15:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-03 15:20 [PATCHSET 0/3] Add throttling for discards Jens Axboe
2018-05-03 15:20 ` [PATCH 1/3] block: break discard submissions into the user defined size Jens Axboe
2018-05-07 9:51 ` Christoph Hellwig
2018-05-07 15:47 ` Jens Axboe
2018-05-03 15:20 ` [PATCH 2/3] blk-wbt: account any writing command as a write Jens Axboe
2018-05-07 9:53 ` Christoph Hellwig
2018-05-03 15:20 ` [PATCH 3/3] blk-wbt: throttle discards like background writes Jens Axboe
2018-05-07 9:57 ` Christoph Hellwig
2018-05-07 15:51 ` Jens Axboe [this message]
2018-05-03 17:45 ` [PATCHSET 0/3] Add throttling for discards 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=d2657561-8c24-9a29-6aa1-01e6548a0d31@kernel.dk \
--to=axboe@kernel.dk \
--cc=dchinner@redhat.com \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-xfs@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).