All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Sameeh Jubran <sameeh@daynix.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	Yan Vugenfirer <yan@daynix.com>, Jason Wang <jasowang@redhat.com>,
	Amnon Ilan <ailan@redhat.com>,
	QEMU Developers <qemu-devel@nongnu.org>,
	"Michael S . Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] [RFC v2 0/2] Add BPF suuport to Qemu
Date: Mon, 25 Jun 2018 16:35:02 +0100	[thread overview]
Message-ID: <20180625153502.GJ18580@redhat.com> (raw)
In-Reply-To: <CAKPgXcGLuY62tnHzo+12OLBaqJWo-_n=D=FLx2oSR9+owHb1zQ@mail.gmail.com>

On Mon, Jun 25, 2018 at 02:21:31PM +0300, Sameeh Jubran wrote:
> On Mon, Jun 25, 2018 at 2:16 PM, Peter Maydell <peter.maydell@linaro.org>
> wrote:
> 
> > On 25 June 2018 at 12:07, Sameeh Jubran <sameeh@daynix.com> wrote:
> > > From: Sameeh Jubran <sjubran@redhat.com>
> > >
> > > The Berkeley Packet Filter has been in the kernel for a while now and I
> > > think it is time that it is introduced to Qemu. This patch is an
> > > infrastructure for any future usage of the BPF in Qemu.
> > >
> > > It is important to note that the tun driver had started supporting using
> > > BPF programs through ioctls (TUNSETSTEERINGEBPF and TUNSETFILTEREBPF).
> > > My plan is to use the bpf support from within virtio-net in order to set
> > > a bpf steering program to the tun device which would allow virtio-net to
> > > support RSS feature https://lists.oasis-open.org/
> > archives/virtio-dev/201805/msg00024.html
> > >
> > > Difference from v1:
> > > * Used libbpf library provided by linux
> > > * Added a configure option
> > > * Added a sample patch with demonstrates how to use the libbpf library
> > >   from within virtio-net. This patch should not be applied! It is for
> > >   demonstration purposes only
> > >
> > > The libbpf can be manually installed from the Linux source tree by
> > running make
> > > tools/bpf and make tools/bpf_install from the top level directory.
> >
> > I'm afraid this series still doesn't have a real use case for the
> > library, which is what we would need to be able to review whether
> > using BPF is a sensible design for whatever the underlying
> > feature to be implemented is. That is, what you should be sending
> > is "here is a patchset to implement RSS in virtio-net (and it
> > happens to be implemented using BPF)", not "here is a patchset
> > which links QEMU with libbpf and does nothing else".
> >
> I don't think the infrastructure should be coupled with the implementation.
> These are two separate patch sets, however I can combine them to one.

FWIW, it is perfectly ok to send the code as 2 separate patch sets if you
want to keep them separated. The key point is simply to be able to see a
real implementation.

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 :|

  reply	other threads:[~2018-06-25 15:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-25 11:07 [Qemu-devel] [RFC v2 0/2] Add BPF suuport to Qemu Sameeh Jubran
2018-06-25 11:07 ` [Qemu-devel] [RFC v2 1/2] Add bpf support to qemu Sameeh Jubran
2018-06-25 11:07 ` [Qemu-devel] [RFC v2 2/2] virtio-net: Example Patch for using BPF Sameeh Jubran
2018-06-25 11:22   ` Daniel P. Berrangé
2018-06-25 15:29     ` Sameeh Jubran
2018-06-25 11:16 ` [Qemu-devel] [RFC v2 0/2] Add BPF suuport to Qemu Peter Maydell
2018-06-25 11:21   ` Sameeh Jubran
2018-06-25 15:35     ` Daniel P. Berrangé [this message]
2018-06-30 18:56 ` no-reply
2018-07-02  5:20 ` no-reply

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=20180625153502.GJ18580@redhat.com \
    --to=berrange@redhat.com \
    --cc=ailan@redhat.com \
    --cc=jasowang@redhat.com \
    --cc=mst@redhat.com \
    --cc=peter.maydell@linaro.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.