From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Sameeh Jubran <sameeh@daynix.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
Jason Wang <jasowang@redhat.com>, Yan Vugenfirer <yan@daynix.com>,
Amnon Ilan <ailan@redhat.com>
Subject: Re: [Qemu-devel] [RFC 0/1] Add BPF suuport to Qemu
Date: Wed, 20 Jun 2018 09:34:59 +0100 [thread overview]
Message-ID: <20180620083459.GB3441@redhat.com> (raw)
In-Reply-To: <CAKPgXcHrZY1=65jOg3Y3bDdwNnik7x-Ti-3PAryYsRuvRWk=iA@mail.gmail.com>
On Tue, Jun 19, 2018 at 05:37:10PM +0300, Sameeh Jubran wrote:
> This patch is actually a preparation for an upcoming patch set that I want
> to integrate into virtio-net which implements the RSS feature. (
> https://lists.oasis-open.org/archives/virtio-dev/201805/msg00024.html)
> So there is a use case. The rationale behind this is to distinguish the
> infrastructure preparation needed for the BPF from the actual RSS feature
> implementation.
Ah, so IIUC, that is not actually doing network filtering, rather it is
some performance related feature than happens to make of use of BPF.
I think it is be important to submit code changes for the virtio driver
at the same time, so we can properly understand the interface and usage
model exposed to the user CLI (if any).
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:[~2018-06-20 8:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-19 13:21 [Qemu-devel] [RFC 0/1] Add BPF suuport to Qemu Sameeh Jubran
2018-06-19 13:22 ` [Qemu-devel] [RFC 1/1] Add BPF support to qemu Sameeh Jubran
2018-06-19 14:41 ` Murilo Opsfelder Araujo
2018-06-19 14:46 ` Sameeh Jubran
2018-06-19 13:37 ` [Qemu-devel] [RFC 0/1] Add BPF suuport to Qemu Peter Maydell
2018-06-19 13:49 ` Daniel P. Berrangé
2018-06-19 14:37 ` Sameeh Jubran
2018-06-20 8:34 ` Daniel P. Berrangé [this message]
2018-06-20 14:43 ` Sameeh Jubran
2018-06-20 8:19 ` Jason Wang
2018-06-19 16:17 ` no-reply
2018-06-20 8:13 ` Jason Wang
2018-06-20 14:40 ` Sameeh Jubran
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=20180620083459.GB3441@redhat.com \
--to=berrange@redhat.com \
--cc=ailan@redhat.com \
--cc=jasowang@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=sameeh@daynix.com \
--cc=yan@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).