From: Oleg Nesterov <oleg@redhat.com>
To: Yu Kuai <yukuai1@huaweicloud.com>
Cc: Li Nan <linan666@huaweicloud.com>,
Khazhy Kumykov <khazhy@chromium.org>,
tj@kernel.org, josef@toxicpanda.com, axboe@kernel.dk,
cgroups@vger.kernel.org, linux-block@vger.kernel.org,
linux-kernel@vger.kernel.org, yi.zhang@huawei.com,
houtao1@huawei.com, yangerkun@huawei.com,
"yukuai (C)" <yukuai3@huawei.com>
Subject: Re: [PATCH] blk-throttle: Calculate allowed value only when the throttle is enabled
Date: Sun, 8 Oct 2023 13:36:03 +0200 [thread overview]
Message-ID: <20231008113602.GB24726@redhat.com> (raw)
In-Reply-To: <21843836-7265-f903-a7d5-e77b07dd5a71@huaweicloud.com>
On 10/08, Yu Kuai wrote:
>
> >> static u64 calculate_bytes_allowed(u64 bps_limit, unsigned long
> >>jiffy_elapsed)
> >> {
> >>+ if (jiffy_elapsed > HZ &&
> >>+ bps_limit > mul_u64_u64_div_u64(U64_MAX, (u64)HZ,
> >>(u64)jiffy_elapsed);
> >>+ return U64_MAX;
> >>+
> >
> >I can't suggest anything better...
> >
> >but I do not know if it is possible that HZ > jiffy_elapsed. If yes, then
> >mul_u64_u64_div_u64() above is not safe too.
>
> Well, 'jiffy_elapsed > HZ' is judged before mul_u64_u64_div_u64().
Yes, sorry, somehow I didn't notice this check.
Oleg.
next prev parent reply other threads:[~2023-10-08 11:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-28 1:58 [PATCH] blk-throttle: Calculate allowed value only when the throttle is enabled linan666
2023-10-04 19:31 ` Tejun Heo
2023-10-04 20:30 ` Khazhy Kumykov
2023-10-04 20:44 ` Khazhy Kumykov
[not found] ` <4ace01e8-6815-29d0-70ce-4632818ca701@huaweicloud.com>
2023-10-05 16:24 ` Oleg Nesterov
2023-10-07 1:23 ` Yu Kuai
2023-10-07 15:16 ` Oleg Nesterov
2023-10-08 1:26 ` Yu Kuai
2023-10-08 11:36 ` Oleg Nesterov [this message]
2023-10-13 21:51 ` Khazhy Kumykov
2023-10-16 1:46 ` Yu Kuai
2023-10-16 20:06 ` Khazhy Kumykov
2023-10-16 21:48 ` Khazhy Kumykov
2023-10-17 2:38 ` Yu Kuai
2023-10-05 17:04 ` Oleg Nesterov
2023-10-05 17:15 ` Khazhy Kumykov
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=20231008113602.GB24726@redhat.com \
--to=oleg@redhat.com \
--cc=axboe@kernel.dk \
--cc=cgroups@vger.kernel.org \
--cc=houtao1@huawei.com \
--cc=josef@toxicpanda.com \
--cc=khazhy@chromium.org \
--cc=linan666@huaweicloud.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@kernel.org \
--cc=yangerkun@huawei.com \
--cc=yi.zhang@huawei.com \
--cc=yukuai1@huaweicloud.com \
--cc=yukuai3@huawei.com \
/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).