From: Andrew Melnychenko <andrew@daynix.com>
To: jasowang@redhat.com, mst@redhat.com, armbru@redhat.com,
eblake@redhat.com, qemu-devel@nongnu.org, berrange@redhat.com
Cc: yuri.benditovich@daynix.com, yan@daynix.com, akihiko.odaki@daynix.com
Subject: [PATCH v8 0/5] eBPF RSS through QMP support.
Date: Thu, 25 Jan 2024 15:06:49 +0200 [thread overview]
Message-ID: <20240125130656.425607-1-andrew@daynix.com> (raw)
This series of patches provides the ability to retrieve eBPF program
through qmp, so management application may load bpf blob with proper capabilities.
Now, virtio-net devices can accept eBPF programs and maps through properties
as external file descriptors. Access to the eBPF map is direct through mmap()
call, so it should not require additional capabilities to bpf* calls.
eBPF file descriptors can be passed to QEMU from parent process or by unix
socket with sendfd() qmp command.
Changes since v8:
* rebased and refactored QMP interface
Changes since v7:
* rebased and refactored
* used SPDX license identifier
* used DEFINE_PROP_ARRAY() for virtio-net "ebpf-rss-fds" property
Changes since v6:
* added comments to ebpf.json
* added libbpf version requirements to meson script with BPF_F_MMAPABLE check
Changes since v5:
* refactored ebpf.json
Changes since v4:
* refactored commit hunks
* added explicit BPF_F_MMAPABLE declaration
Changes since v3:
* fixed issue with the build if bpf disabled
* rebased to the last master
* refactored according to review
Changes since v2:
* moved/refactored QMP command
* refactored virtio-net
Changes since v1:
* refactored virtio-net
* moved hunks for ebpf mmap()
* added qmp enum for eBPF id.
Andrew Melnychenko (5):
ebpf: Added eBPF map update through mmap.
ebpf: Added eBPF initialization by fds.
virtio-net: Added property to load eBPF RSS with fds.
qmp: Added new command to retrieve eBPF blob.
ebpf: Updated eBPF program and skeleton.
ebpf/ebpf.c | 69 ++
ebpf/ebpf.h | 29 +
ebpf/ebpf_rss-stub.c | 9 +-
ebpf/ebpf_rss.c | 153 +++-
ebpf/ebpf_rss.h | 13 +-
ebpf/meson.build | 2 +-
ebpf/rss.bpf.skeleton.h | 1343 ++++++++++++++++----------------
hw/net/virtio-net.c | 63 +-
include/hw/virtio/virtio-net.h | 2 +
meson.build | 10 +-
qapi/ebpf.json | 66 ++
qapi/meson.build | 1 +
qapi/qapi-schema.json | 1 +
tools/ebpf/rss.bpf.c | 7 +-
14 files changed, 1059 insertions(+), 709 deletions(-)
create mode 100644 ebpf/ebpf.c
create mode 100644 ebpf/ebpf.h
create mode 100644 qapi/ebpf.json
--
2.43.0
next reply other threads:[~2024-01-25 13:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-25 13:06 Andrew Melnychenko [this message]
2024-01-25 13:06 ` [PATCH v8 1/5] ebpf: Added eBPF map update through mmap Andrew Melnychenko
2024-01-30 10:37 ` Daniel P. Berrangé
2024-02-05 16:54 ` Andrew Melnichenko
2024-01-25 13:06 ` [PATCH v8 2/5] ebpf: Added eBPF initialization by fds Andrew Melnychenko
2024-01-25 13:06 ` [PATCH v8 3/5] virtio-net: Added property to load eBPF RSS with fds Andrew Melnychenko
2024-01-25 13:06 ` [PATCH v8 4/5] qmp: Added new command to retrieve eBPF blob Andrew Melnychenko
2024-01-25 13:06 ` [PATCH v8 5/5] ebpf: Updated eBPF program and skeleton Andrew Melnychenko
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=20240125130656.425607-1-andrew@daynix.com \
--to=andrew@daynix.com \
--cc=akihiko.odaki@daynix.com \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=eblake@redhat.com \
--cc=jasowang@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=yan@daynix.com \
--cc=yuri.benditovich@daynix.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;
as well as URLs for NNTP newsgroup(s).