From: Edward Cree <ecree@solarflare.com>
To: David Miller <davem@davemloft.net>
Cc: <ast@fb.com>, <daniel@iogearbox.net>,
<alexei.starovoitov@gmail.com>, <netdev@vger.kernel.org>
Subject: Re: [PATCH v2 1/3] bpf: Use 1<<16 as ceiling for immediate alignment in verifier.
Date: Thu, 18 May 2017 15:10:03 +0100 [thread overview]
Message-ID: <d348799b-4404-b408-9c36-59885c811eed@solarflare.com> (raw)
In-Reply-To: <20170517.201633.1413407173876329751.davem@davemloft.net>
On 18/05/17 01:16, David Miller wrote:
> So, in C, addition (a += b) is something like:
>
> struct bpf_reg_bits {
> u64 zero_bits;
> u64 one_bits;
> };
>
> static void add_update_bits(struct bpf_reg_bits *a, struct bpf_reg_bits *b)
> {
> u64 m_zeros, m_ones, m_all;
>
> m_zeros = a->zero_bits ^ b->zero_bits;
> m_ones = a->one_bits ^ b->one_bits;
> m_all = m_zeros | m_ones;
No, this should be
u64 m_a, m_b, m_all;
m_a = a->zero_bits ^ a->one_bits; /* unknown bits in a */
m_b = b->zero_bits ^ b->one_bits; /* unknown bits in b */
m_all = m_a | m_b; /* unknown bits in result */
> a->zero_bits = (a->zero_bits + b->zero_bits) | m_all;
> a->one_bits = (a->one_bits + b->zero_bits) & ~m_all;
> }
>
> Then, is subtraction merely:
>
> static void sub_update_bits(struct bpf_reg_bits *a, struct bpf_reg_bits *b)
> {
> u64 m_zeros, m_ones, m_all;
>
> m_zeros = a->zero_bits ^ b->zero_bits;
> m_ones = a->one_bits ^ b->one_bits;
> m_all = m_zeros | m_ones;
>
> a->zero_bits = (a->zero_bits - b->zero_bits) | m_all;
> a->one_bits = (a->one_bits - b->zero_bits) & ~m_all;
> }
>
> Or is something different needed?
I suspect it's something different, just because I worry about what
carries will do.
But I think Alexei's idea (mask and value) is better anyway; at the
least it's easier to think about.
-Ed
next prev parent reply other threads:[~2017-05-18 14:10 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-15 16:04 [PATCH v2 1/3] bpf: Use 1<<16 as ceiling for immediate alignment in verifier David Miller
2017-05-16 12:37 ` Edward Cree
2017-05-16 19:52 ` David Miller
2017-05-16 22:53 ` Alexei Starovoitov
2017-05-17 14:00 ` Edward Cree
2017-05-17 15:33 ` Edward Cree
2017-05-18 0:16 ` David Miller
2017-05-18 1:18 ` Alexei Starovoitov
2017-05-18 14:10 ` Edward Cree [this message]
2017-05-18 2:48 ` Alexei Starovoitov
2017-05-18 14:49 ` Edward Cree
2017-05-18 16:38 ` Edward Cree
2017-05-18 18:41 ` Edward Cree
2017-05-19 1:22 ` Alexei Starovoitov
2017-05-19 14:21 ` Edward Cree
2017-05-19 14:55 ` Alexei Starovoitov
2017-05-19 17:17 ` Edward Cree
2017-05-19 20:00 ` Alignment in BPF verifier Edward Cree
2017-05-19 20:39 ` David Miller
2017-05-19 23:05 ` Daniel Borkmann
2017-05-23 14:41 ` Edward Cree
2017-05-23 17:43 ` Edward Cree
2017-05-23 23:59 ` Alexei Starovoitov
2017-05-23 19:45 ` Alexei Starovoitov
2017-05-23 21:27 ` Daniel Borkmann
2017-05-24 13:46 ` Edward Cree
2017-05-24 16:39 ` Alexei Starovoitov
2017-05-25 16:31 ` David Miller
2017-05-19 20:48 ` David Miller
2017-05-19 20:41 ` [PATCH v2 1/3] bpf: Use 1<<16 as ceiling for immediate alignment in verifier David Miller
2017-05-19 21:37 ` Alexei Starovoitov
2017-05-19 23:16 ` David Miller
2017-05-20 0:20 ` Alexei Starovoitov
2017-05-17 16:13 ` David Miller
2017-05-17 17:00 ` Edward Cree
2017-05-17 17:25 ` David Miller
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=d348799b-4404-b408-9c36-59885c811eed@solarflare.com \
--to=ecree@solarflare.com \
--cc=alexei.starovoitov@gmail.com \
--cc=ast@fb.com \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=netdev@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.