Hi, > Got something I could git-pull? > I can share some links for tests: https://github.com/daynix/qemu/tree/HelperEBPFv3 - qemu with helper https://github.com/daynix/libvirt/tree/RSS_RFC_v1 - libvirt with RSS
On Tue, Aug 31, 2021 at 6:00 PM Markus Armbruster <arm...@redhat.com> wrote: > Yuri Benditovich <yuri.benditov...@daynix.com> writes: > > > On Mon, Aug 30, 2021 at 11:14 AM Markus Armbruster <arm...@redhat.com> > wrote: > >> > >> Yuri Benditovich <yuri.benditov...@daynix.com> writes: > >> > >> > On Mon, Aug 30, 2021 at 9:10 AM Markus Armbruster <arm...@redhat.com> > wrote: > > [...] > > >> >> So let's try again: if libvirt does use the wrong RSS helper, how > does > >> >> the system behave? > >> > > >> > The receive-side scaling may work incorrectly, i.e. finally may move > >> > incoming packets to a virtqueue different than expected one. > >> > >> Then I'm confused about the purpose of "the stamp" mentioned below. Can > >> you enlighten me? > > > > The stamp is a string (common for qemu executable and RSS helper > > executable during build) that qemu can later retrieve from the helper > > in run-time and ensure this helper is fully compatible with this build > > of qemu (in terms of eBPF operation). The helper is built with the > > same C headers (related to ebpf operation) as the qemu, the qemu is > > able to receive file descriptors created by the helper (of ebpf > > program and ebpf data structure's maps) from libvirt and deal with > > them as if it has created them. > > Thanks. > > I tried to apply your series to check a few of my assumptions, but I'm > getting conflicts. Got something I could git-pull? > > [...] > >
