From: "Toke Høiland-Jørgensen" <toke@redhat.com>
To: Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
Jesper Dangaard Brouer <hawk@kernel.org>,
John Fastabend <john.fastabend@gmail.com>
Cc: "Toke Høiland-Jørgensen" <toke@redhat.com>,
netdev@vger.kernel.org, bpf@vger.kernel.org
Subject: [PATCH bpf-next v3 0/3] A couple of small refactorings of BPF program call sites
Date: Tue, 8 Nov 2022 15:05:58 +0100 [thread overview]
Message-ID: <20221108140601.149971-1-toke@redhat.com> (raw)
Stanislav suggested[0] that these small refactorings could be split out from the
XDP queueing RFC series and merged separately. The first change is a small
repacking of struct softnet_data, the others change the BPF call sites to
support full 64-bit values as arguments to bpf_redirect_map() and as the return
value of a BPF program, relying on the fact that BPF registers are always 64-bit
wide to maintain backwards compatibility.
Please see the individual patches for details.
v3:
- In patch 3, don't change types of return values that are copied to
userspace (which should fix selftest errors on big-endian archs like s390)
- Rebase on bpf-next
- Collect Song's ACKs
v2:
- Rebase on bpf-next (CI failure seems to be unrelated to this series)
- Collect Stanislav's Reviewed-by
[0] https://lore.kernel.org/r/CAKH8qBtdnku7StcQ-SamadvAF==DRuLLZO94yOR1WJ9Bg=uX1w@mail.gmail.com
Kumar Kartikeya Dwivedi (1):
bpf: Use 64-bit return value for bpf_prog_run
Toke Høiland-Jørgensen (2):
dev: Move received_rps counter next to RPS members in softnet data
bpf: Expand map key argument of bpf_redirect_map to u64
include/linux/bpf-cgroup.h | 12 +++++------
include/linux/bpf.h | 24 +++++++++++-----------
include/linux/filter.h | 42 +++++++++++++++++++-------------------
include/linux/netdevice.h | 2 +-
include/uapi/linux/bpf.h | 2 +-
kernel/bpf/cgroup.c | 12 +++++------
kernel/bpf/core.c | 14 ++++++-------
kernel/bpf/cpumap.c | 4 ++--
kernel/bpf/devmap.c | 4 ++--
kernel/bpf/offload.c | 4 ++--
kernel/bpf/verifier.c | 2 +-
net/core/filter.c | 4 ++--
net/packet/af_packet.c | 7 +++++--
net/xdp/xskmap.c | 4 ++--
14 files changed, 70 insertions(+), 67 deletions(-)
--
2.38.1
next reply other threads:[~2022-11-08 14:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-08 14:05 Toke Høiland-Jørgensen [this message]
2022-11-08 14:05 ` [PATCH bpf-next v3 1/3] dev: Move received_rps counter next to RPS members in softnet data Toke Høiland-Jørgensen
2022-11-08 14:06 ` [PATCH bpf-next v3 2/3] bpf: Expand map key argument of bpf_redirect_map to u64 Toke Høiland-Jørgensen
2022-11-08 14:06 ` [PATCH bpf-next v3 3/3] bpf: Use 64-bit return value for bpf_prog_run Toke Høiland-Jørgensen
2022-11-15 17:09 ` Alexei Starovoitov
2022-11-15 19:39 ` Kumar Kartikeya Dwivedi
2022-11-15 17:10 ` [PATCH bpf-next v3 0/3] A couple of small refactorings of BPF program call sites 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=20221108140601.149971-1-toke@redhat.com \
--to=toke@redhat.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=hawk@kernel.org \
--cc=john.fastabend@gmail.com \
--cc=kuba@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox