From: David Vernet <void@manifault.com>
To: Dave Thaler <dthaler1968@googlemail.com>
Cc: bpf@vger.kernel.org, bpf@ietf.org,
Dave Thaler <dthaler@microsoft.com>,
eddyz87@gmail.com
Subject: Re: [PATCH bpf-next] bpf, docs: Define signed modulo as using truncated division
Date: Wed, 18 Oct 2023 17:28:59 -0500 [thread overview]
Message-ID: <20231018222859.GD4176@maniforge> (raw)
In-Reply-To: <20231017203020.1500-1-dthaler1968@googlemail.com>
On Tue, Oct 17, 2023 at 08:30:20PM +0000, Dave Thaler wrote:
> From: Dave Thaler <dthaler@microsoft.com>
>
> There's different mathematical definitions (truncated, floored,
> rounded, etc.) and different languages have chosen different
> definitions [0][1]. E.g., languages/libraries that follow Knuth
> use a different mathematical definition than C uses. This
> patch specifies which definition BPF uses, as verified by
> Eduard [2] and others.
>
> [0]: https://en.wikipedia.org/wiki/Modulo#Variants_of_the_definition
> [1]: https://torstencurdt.com/tech/posts/modulo-of-negative-numbers/
> [2]: https://lore.kernel.org/bpf/57e6fefadaf3b2995bb259fa8e711c7220ce5290.camel@gmail.com/
>
> Signed-off-by: Dave Thaler <dthaler@microsoft.com>
Acked-by: David Vernet <void@manifault.com>
+cc Eduard as well in case he wants to take a look.
> ---
> Documentation/bpf/standardization/instruction-set.rst | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/Documentation/bpf/standardization/instruction-set.rst b/Documentation/bpf/standardization/instruction-set.rst
> index c5d53a6e8c7..245b6defc29 100644
> --- a/Documentation/bpf/standardization/instruction-set.rst
> +++ b/Documentation/bpf/standardization/instruction-set.rst
> @@ -283,6 +283,14 @@ For signed operations (``BPF_SDIV`` and ``BPF_SMOD``), for ``BPF_ALU``,
> is first :term:`sign extended<Sign Extend>` from 32 to 64 bits, and then
> interpreted as a 64-bit signed value.
>
> +Note that there are varying definitions of the signed modulo operation
> +when the dividend or divisor are negative, where implementations often
> +vary by language such that Python, Ruby, etc. differ from C, Go, Java,
> +etc. This specification requires that signed modulo use truncated division
> +(where -13 % 3 == -1) as implemented in C, Go, etc.:
> +
> + a % n = a - n * trunc(a / n)
> +
> The ``BPF_MOVSX`` instruction does a move operation with sign extension.
> ``BPF_ALU | BPF_MOVSX`` :term:`sign extends<Sign Extend>` 8-bit and 16-bit operands into 32
> bit operands, and zeroes the remaining upper 32 bits.
> --
> 2.33.4
>
>
WARNING: multiple messages have this Message-ID (diff)
From: David Vernet <void@manifault.com>
To: Dave Thaler <dthaler1968@googlemail.com>
Cc: bpf@vger.kernel.org, bpf@ietf.org,
Dave Thaler <dthaler@microsoft.com>,
eddyz87@gmail.com
Subject: Re: [Bpf] [PATCH bpf-next] bpf, docs: Define signed modulo as using truncated division
Date: Wed, 18 Oct 2023 17:28:59 -0500 [thread overview]
Message-ID: <20231018222859.GD4176@maniforge> (raw)
Message-ID: <20231018222859.L_Dti6XV36EF3Q0bcKw9GLCbnrGE4R5E3rHR5iTkQ0w@z> (raw)
In-Reply-To: <20231017203020.1500-1-dthaler1968@googlemail.com>
On Tue, Oct 17, 2023 at 08:30:20PM +0000, Dave Thaler wrote:
> From: Dave Thaler <dthaler@microsoft.com>
>
> There's different mathematical definitions (truncated, floored,
> rounded, etc.) and different languages have chosen different
> definitions [0][1]. E.g., languages/libraries that follow Knuth
> use a different mathematical definition than C uses. This
> patch specifies which definition BPF uses, as verified by
> Eduard [2] and others.
>
> [0]: https://en.wikipedia.org/wiki/Modulo#Variants_of_the_definition
> [1]: https://torstencurdt.com/tech/posts/modulo-of-negative-numbers/
> [2]: https://lore.kernel.org/bpf/57e6fefadaf3b2995bb259fa8e711c7220ce5290.camel@gmail.com/
>
> Signed-off-by: Dave Thaler <dthaler@microsoft.com>
Acked-by: David Vernet <void@manifault.com>
+cc Eduard as well in case he wants to take a look.
> ---
> Documentation/bpf/standardization/instruction-set.rst | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/Documentation/bpf/standardization/instruction-set.rst b/Documentation/bpf/standardization/instruction-set.rst
> index c5d53a6e8c7..245b6defc29 100644
> --- a/Documentation/bpf/standardization/instruction-set.rst
> +++ b/Documentation/bpf/standardization/instruction-set.rst
> @@ -283,6 +283,14 @@ For signed operations (``BPF_SDIV`` and ``BPF_SMOD``), for ``BPF_ALU``,
> is first :term:`sign extended<Sign Extend>` from 32 to 64 bits, and then
> interpreted as a 64-bit signed value.
>
> +Note that there are varying definitions of the signed modulo operation
> +when the dividend or divisor are negative, where implementations often
> +vary by language such that Python, Ruby, etc. differ from C, Go, Java,
> +etc. This specification requires that signed modulo use truncated division
> +(where -13 % 3 == -1) as implemented in C, Go, etc.:
> +
> + a % n = a - n * trunc(a / n)
> +
> The ``BPF_MOVSX`` instruction does a move operation with sign extension.
> ``BPF_ALU | BPF_MOVSX`` :term:`sign extends<Sign Extend>` 8-bit and 16-bit operands into 32
> bit operands, and zeroes the remaining upper 32 bits.
> --
> 2.33.4
>
>
--
Bpf mailing list
Bpf@ietf.org
https://www.ietf.org/mailman/listinfo/bpf
next prev parent reply other threads:[~2023-10-18 22:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-17 20:30 [PATCH bpf-next] bpf, docs: Define signed modulo as using truncated division Dave Thaler
2023-10-17 20:30 ` [Bpf] " Dave Thaler
2023-10-18 22:28 ` David Vernet [this message]
2023-10-18 22:28 ` David Vernet
2023-10-18 22:34 ` Eduard Zingerman
2023-10-18 23:40 ` Daniel Borkmann
2023-10-18 23:40 ` [Bpf] " Daniel Borkmann
2023-10-19 0:00 ` Eduard Zingerman
2023-10-19 0:00 ` [Bpf] " Eduard Zingerman
2023-10-18 23:40 ` patchwork-bot+netdevbpf
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=20231018222859.GD4176@maniforge \
--to=void@manifault.com \
--cc=bpf@ietf.org \
--cc=bpf@vger.kernel.org \
--cc=dthaler1968@googlemail.com \
--cc=dthaler@microsoft.com \
--cc=eddyz87@gmail.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