From: SJ Park <sj@kernel.org>
To: Wang Guangke <gkwang@linx-info.com>
Cc: SJ Park <sj@kernel.org>,
akpm@linux-foundation.org, damon@lists.linux.dev,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm/damon/stat: avoid overflow in estimated_memory_bandwidth calculation
Date: Mon, 2 Nov 2026 06:25:28 -0800 [thread overview]
Message-ID: <20261102142528.27792-1-sj@kernel.org> (raw)
In-Reply-To: <auhgJ74TeQOIvTtO@DiGouShu>
On Mon, 2 Nov 2026 18:04:23 +0800 Wang Guangke <gkwang@linx-info.com> wrote:
> Hi SJ,
> Thanks for your review.
>
> On Sun, Nov 01, 2026 at 11:13:43AM -0800, SJ Park wrote:
> > Hello Wang,
> >
> > On Mon, 2 Nov 2026 02:00:01 +0800 Wang Guangke <gkwang@linx-info.com> wrote:
> >
> > > The calculation of estimated_memory_bandwidth computes
> > > access_bytes * USEC_PER_MSEC * MSEC_PER_SEC / aggr_interval directly.
> > > On 32-bit systems, the intermediate product
> > > access_bytes * USEC_PER_MSEC * MSEC_PER_SEC may overflow before the
> > > division is performed.
> >
> > Do you find this issue from real usage? Or, jsut theoretical? Could you
> > please clarify it, and user impacts of the issue?
>
> I found it by code inspection, not from real usage on a 32-bit system.
Thank you for clarifying.
[...]
> > > + estimated_memory_bandwidth =
> > > + bytes_per_interval * USEC_PER_MSEC * MSEC_PER_SEC +
> > > + div64_u64(remainder * USEC_PER_MSEC * MSEC_PER_SEC,
> > > + c->attrs.aggr_interval);
> >
> > Let's use USEC_PER_SEC instead of 'USEC_PER_MSEC * MSEC_PER_SEC'.
>
> Thanks, I will rename the variable to bytes_per_us, and use USEC_PER_SEC
> instead of 'USEC_PER_MSEC * MSEC_PER_SEC'.
Thank you for accepting my humble suggestions. Looking forward to v2.
Thanks,
SJ
[...]
prev parent reply other threads:[~2026-11-02 14:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-01 18:00 Wang Guangke
2026-11-01 19:13 ` SJ Park
2026-11-02 10:04 ` Wang Guangke
2026-11-02 14:25 ` SJ Park [this message]
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=20261102142528.27792-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=damon@lists.linux.dev \
--cc=gkwang@linx-info.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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
all inboxes | Powered by JetHome®