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
Subject: [PATCH v2 0/6] eBPF RSS through QMP support.
Date: Fri, 12 May 2023 15:28:56 +0300 [thread overview]
Message-ID: <20230512122902.34345-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 v1:
* refactored code.
* eBPF program ids implemented as enums
Andrew Melnychenko (6):
ebpf: Added eBPF map update through mmap.
ebpf: Added eBPF initialization by fds.
virtio-net: Added property to load eBPF RSS with fds.
ebpf: Added declaration/initialization routines.
qmp: Added new command to retrieve eBPF blob.
ebpf: Updated eBPF program and skeleton.
ebpf/ebpf.c | 54 ++
ebpf/ebpf.h | 31 +
ebpf/ebpf_rss-stub.c | 6 +
ebpf/ebpf_rss.c | 149 +++-
ebpf/ebpf_rss.h | 10 +
ebpf/meson.build | 1 +
ebpf/rss.bpf.skeleton.h | 1469 ++++++++++++++++----------------
hw/net/virtio-net.c | 55 +-
include/hw/virtio/virtio-net.h | 1 +
monitor/qmp-cmds.c | 16 +
qapi/misc.json | 38 +
tools/ebpf/rss.bpf.c | 2 +-
12 files changed, 1073 insertions(+), 759 deletions(-)
create mode 100644 ebpf/ebpf.c
create mode 100644 ebpf/ebpf.h
--
2.39.1
next reply other threads:[~2023-05-12 12:48 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-12 12:28 Andrew Melnychenko [this message]
2023-05-12 12:28 ` [PATCH v2 1/6] ebpf: Added eBPF map update through mmap Andrew Melnychenko
2023-05-15 9:34 ` Daniel P. Berrangé
2023-05-12 12:28 ` [PATCH v2 2/6] ebpf: Added eBPF initialization by fds Andrew Melnychenko
2023-05-15 9:35 ` Daniel P. Berrangé
2023-05-12 12:28 ` [PATCH v2 3/6] virtio-net: Added property to load eBPF RSS with fds Andrew Melnychenko
2023-05-15 9:38 ` Daniel P. Berrangé
2023-05-15 10:53 ` Andrew Melnichenko
2023-05-16 21:21 ` Eric Blake
2023-05-12 12:29 ` [PATCH v2 4/6] ebpf: Added declaration/initialization routines Andrew Melnychenko
2023-05-15 9:44 ` Daniel P. Berrangé
2023-05-12 12:29 ` [PATCH v2 5/6] qmp: Added new command to retrieve eBPF blob Andrew Melnychenko
2023-05-15 9:50 ` Daniel P. Berrangé
2023-05-16 8:47 ` Markus Armbruster
2023-05-16 8:54 ` Daniel P. Berrangé
2023-05-16 10:23 ` Markus Armbruster
2023-05-16 10:29 ` Daniel P. Berrangé
2023-05-16 14:04 ` Markus Armbruster
2023-05-16 14:35 ` Daniel P. Berrangé
2023-05-16 15:06 ` Markus Armbruster
2023-05-16 15:18 ` Daniel P. Berrangé
2023-05-22 10:50 ` Markus Armbruster
2023-05-12 12:29 ` [PATCH v2 6/6] ebpf: Updated eBPF program and skeleton Andrew Melnychenko
2023-05-15 9:53 ` Daniel P. Berrangé
2023-05-16 21:29 ` Eric Blake
2023-05-12 12:31 ` [PATCH v2 0/6] eBPF RSS through QMP support Andrew Melnichenko
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=20230512122902.34345-1-andrew@daynix.com \
--to=andrew@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).