From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Jason Wang <jasowang@redhat.com>
Cc: Andrew Melnychenko <andrew@daynix.com>,
mst@redhat.com, pbonzini@redhat.com, marcandre.lureau@redhat.com,
thuth@redhat.com, philmd@linaro.org, armbru@redhat.com,
eblake@redhat.com, qemu-devel@nongnu.org, toke@redhat.com,
mprivozn@redhat.com, yuri.benditovich@daynix.com, yan@daynix.com
Subject: Re: [RFC PATCH 1/5] ebpf: Added eBPF initialization by fds and map update.
Date: Thu, 30 Mar 2023 08:10:27 +0100 [thread overview]
Message-ID: <ZCU1497ElEvDbwnG@redhat.com> (raw)
In-Reply-To: <CACGkMEuiEgerMzuZvykQ=8ML5CW9rdi4h6da5tDeuxER-jSPuw@mail.gmail.com>
On Thu, Mar 30, 2023 at 02:53:16PM +0800, Jason Wang wrote:
> On Thu, Mar 30, 2023 at 8:33 AM Andrew Melnychenko <andrew@daynix.com> wrote:
> >
> > Changed eBPF map updates through mmaped array.
> > Mmaped arrays provide direct access to map data.
> > It should omit using bpf_map_update_elem() call,
> > which may require capabilities that are not present.
>
> This requires kernel support, so after this change, eBPF based RSS
> doesn't work on old kernels that only support syscall based map
> updating.
What kernel version is the cut off ?
With regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2023-03-30 7:11 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-30 0:15 [RFC PATCH 0/4] eBPF RSS through QMP support Andrew Melnychenko
2023-03-30 0:15 ` [RFC PATCH 1/5] ebpf: Added eBPF initialization by fds and map update Andrew Melnychenko
2023-03-30 6:53 ` Jason Wang
2023-03-30 6:56 ` Jason Wang
2023-03-30 7:10 ` Daniel P. Berrangé [this message]
2023-03-30 11:13 ` Andrew Melnichenko
2023-03-30 0:15 ` [RFC PATCH 2/5] virtio-net: Added property to load eBPF RSS with fds Andrew Melnychenko
2023-03-30 8:52 ` Daniel P. Berrangé
2023-03-30 0:15 ` [RFC PATCH 3/5] ebpf: Added declaration/initialization routines Andrew Melnychenko
2023-03-30 6:54 ` Jason Wang
2023-03-30 8:34 ` Daniel P. Berrangé
2023-03-31 7:48 ` Jason Wang
2023-03-31 7:59 ` Daniel P. Berrangé
2023-03-31 8:03 ` Jason Wang
2023-03-31 8:13 ` Daniel P. Berrangé
2023-03-31 8:21 ` Jason Wang
2023-03-30 8:33 ` Daniel P. Berrangé
2023-03-30 11:02 ` Andrew Melnichenko
2023-03-30 0:15 ` [RFC PATCH 4/5] qmp: Added new command to retrieve eBPF blob Andrew Melnychenko
2023-03-30 8:39 ` Daniel P. Berrangé
2023-03-30 10:42 ` Andrew Melnichenko
2023-03-30 0:15 ` [RFC PATCH 5/5] ebpf: Updated eBPF program and skeleton Andrew Melnychenko
2023-03-30 6:57 ` [RFC PATCH 0/4] eBPF RSS through QMP support Jason Wang
2023-03-30 10:48 ` 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=ZCU1497ElEvDbwnG@redhat.com \
--to=berrange@redhat.com \
--cc=andrew@daynix.com \
--cc=armbru@redhat.com \
--cc=eblake@redhat.com \
--cc=jasowang@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=mprivozn@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
--cc=toke@redhat.com \
--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).