From: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
To: David CARLIER <devnexen@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Josh Law <objecting@objecting.org>,
Dennis Zhou <dennis@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] lib: fix compare_delta parameter order in percpu_counter_tree
Date: Mon, 16 Mar 2026 09:06:36 -0400 [thread overview]
Message-ID: <d6daa213-62bc-4dca-b9b1-3e1579f8f874@efficios.com> (raw)
In-Reply-To: <CA+XhMqz=v_Ka=+VTB__NjLKsCzEJ31HeMNFDreAi5dVJOO3CrA@mail.gmail.com>
On 2026-03-16 00:28, David CARLIER wrote:
> You're right. Here's the simplified version:
>
Much better. So this covers percpu_counter_tree_approximate_compare_value.
Can we also add coverage for the following affected APIs ?
- percpu_counter_tree_precise_compare_value
- percpu_counter_tree_precise_compare
- percpu_counter_tree_approximate_compare
When comparing between two sets of counters, we end up summing the
the accuracy ranges of the two counters. So in case we ever have an
issue there, it would be good to add coverage of the range limit cases
in the same way.
Thanks,
Mathieu
--
Mathieu Desnoyers
EfficiOS Inc.
https://www.efficios.com
next prev parent reply other threads:[~2026-03-16 13:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-13 17:54 David Carlier
2026-03-14 15:30 ` Josh Law
2026-03-14 21:45 ` Andrew Morton
2026-03-15 22:00 ` Mathieu Desnoyers
2026-03-15 22:47 ` David CARLIER
2026-03-15 23:16 ` Mathieu Desnoyers
2026-03-16 0:05 ` David CARLIER
2026-03-16 0:41 ` Mathieu Desnoyers
2026-03-16 4:28 ` David CARLIER
2026-03-16 13:06 ` Mathieu Desnoyers [this message]
2026-03-16 13:41 ` David CARLIER
2026-03-16 13:53 ` Mathieu Desnoyers
2026-03-16 14:15 ` David CARLIER
2026-03-16 14:15 ` David CARLIER
2026-03-16 14:23 ` Mathieu Desnoyers
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=d6daa213-62bc-4dca-b9b1-3e1579f8f874@efficios.com \
--to=mathieu.desnoyers@efficios.com \
--cc=akpm@linux-foundation.org \
--cc=dennis@kernel.org \
--cc=devnexen@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=objecting@objecting.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®