From: hanjinke <hanjinke.666@bytedance.com>
To: "Michal Koutný" <mkoutny@suse.com>
Cc: tj@kernel.org, josef@toxicpanda.com, axboe@kernel.dk,
cgroups@vger.kernel.org, linux-block@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [External] Re: [PATCH v2] blk-throttle: Fix io statistics for cgroup v1
Date: Tue, 4 Apr 2023 01:56:51 +0800 [thread overview]
Message-ID: <cb69bf15-6288-e5d9-08c9-cf64187ddd03@bytedance.com> (raw)
In-Reply-To: <20230403153021.z4smxxnxbgdcgcey@blackpad>
在 2023/4/3 下午11:30, Michal Koutný 写道:
> On Sat, Apr 01, 2023 at 05:47:08PM +0800, Jinke Han <hanjinke.666@bytedance.com> wrote:
>> From: Jinke Han <hanjinke.666@bytedance.com>
>>
>> After commit f382fb0bcef4 ("block: remove legacy IO schedulers"),
>> blkio.throttle.io_serviced and blkio.throttle.io_service_bytes become
>> the only stable io stats interface of cgroup v1,
>
> There is also blkio.bfq.{io_serviced,io_service_bytes} couple, so it's
> not the only. Or do you mean stable in terms of used IO scheduler?
>
Oh, the stable here means that it always exists, and when the bfq
scheduler is not used, the bfq interface may not exist.
>> and these statistics are done in the blk-throttle code. But the
>> current code only counts the bios that are actually throttled. When
>> the user does not add the throttle limit,
>
> ... "or the limit doesn't kick in"
>
Agree.
>> the io stats for cgroup v1 has nothing.
>
>
>> I fix it according to the statistical method of v2, and made it count
>> all ios accurately.
>
> s/all ios/all bios and split ios/
>
> (IIUC you fix two things)
>
>> Fixes: a7b36ee6ba29 ("block: move blk-throtl fast path inline")
>
> Good catch.
>
> Does it also undo the performance gain from that commit? (Or rather,
> have you observed effect of your patch on v2-only performance?)
>
Under v1, this statistical overhead is unavoidable. Under v2, the static
key is friendly to judging branches, so I think the performance
difference before and after the patch is negligible.
>> Signed-off-by: Jinke Han <hanjinke.666@bytedance.com>
>> ---
>> block/blk-cgroup.c | 6 ++++--
>> block/blk-throttle.c | 6 ------
>> block/blk-throttle.h | 9 +++++++++
>> 3 files changed, 13 insertions(+), 8 deletions(-)
>
> The code looks correct.
>
> Thanks,
> Michal
Thanks.
next prev parent reply other threads:[~2023-04-03 17:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-01 9:47 [PATCH v2] blk-throttle: Fix io statistics for cgroup v1 Jinke Han
2023-04-03 15:30 ` Michal Koutný
2023-04-03 17:56 ` hanjinke [this message]
2023-04-28 19:05 ` Andrea Righi
2023-05-04 15:08 ` [External] " hanjinke
2023-05-04 21:13 ` Andrea Righi
2023-05-05 13:35 ` hanjinke
2023-05-06 11:44 ` Andrea Righi
2023-05-07 15:32 ` hanjinke
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=cb69bf15-6288-e5d9-08c9-cf64187ddd03@bytedance.com \
--to=hanjinke.666@bytedance.com \
--cc=axboe@kernel.dk \
--cc=cgroups@vger.kernel.org \
--cc=josef@toxicpanda.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mkoutny@suse.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