From: Pavel Begunkov <asml.silence@gmail.com>
To: Tejun Heo <tj@kernel.org>, axboe@kernel.dk
Cc: linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel-team@fb.com, cgroups@vger.kernel.org, newella@fb.com,
josef@toxicpanda.com, ming.lei@redhat.com, bvanassche@acm.org
Subject: Re: [PATCHSET v2 block/for-5.8] iocost: improve use_delay and latency target handling
Date: Mon, 13 Apr 2020 20:00:29 +0300 [thread overview]
Message-ID: <6f69d35c-c593-f140-c351-c7fd2c13069e@gmail.com> (raw)
In-Reply-To: <dd55f890-740c-16b5-77bd-4c6fdb710b3d@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 498 bytes --]
On 13/04/2020 19:56, Pavel Begunkov wrote:
> On 13/04/2020 19:27, Tejun Heo wrote:
>> Changes from v1[1]
>>
>> * Dropped 0002-block-add-request-io_data_len.patch and updated to use
>> rq->stats_sectors instead as suggested by Pavel Begunkov.
>
> rq->stats_sectors is set only when there is QUEUE_FLAG_STATS, see
> blk_mq_start_request(). I don't see blk-iocost requiring it. Did I miss something?
And there is no reason to not initialise it unconditionally.
--
Pavel Begunkov
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-04-13 17:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-13 16:27 [PATCHSET v2 block/for-5.8] iocost: improve use_delay and latency target handling Tejun Heo
2020-04-13 16:27 ` [PATCH 1/4] blk-iocost: switch to fixed non-auto-decaying use_delay Tejun Heo
2020-04-13 16:27 ` [PATCH 2/4] blk-iocost: account for IO size when testing latencies Tejun Heo
2020-04-13 16:27 ` [PATCH 3/4] iocost_monitor: exit successfully if interval is zero Tejun Heo
2020-04-13 16:27 ` [PATCH 4/4] iocost_monitor: drop string wrap around numbers when outputting json Tejun Heo
2020-04-13 16:56 ` [PATCHSET v2 block/for-5.8] iocost: improve use_delay and latency target handling Pavel Begunkov
2020-04-13 17:00 ` Pavel Begunkov [this message]
2020-04-13 17:08 ` Tejun Heo
2020-04-13 18:49 ` Pavel Begunkov
2020-04-30 21:55 ` 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=6f69d35c-c593-f140-c351-c7fd2c13069e@gmail.com \
--to=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--cc=bvanassche@acm.org \
--cc=cgroups@vger.kernel.org \
--cc=josef@toxicpanda.com \
--cc=kernel-team@fb.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.lei@redhat.com \
--cc=newella@fb.com \
--cc=tj@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).