From: Thomas Graf <tgraf@noironetworks.com>
To: Andy Zhou <azhou@nicira.com>
Cc: "dev@openvswitch.com" <dev@openvswitch.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [ovs-dev] OVS + BPF, make sense?
Date: Mon, 22 Dec 2014 10:53:21 +0100 [thread overview]
Message-ID: <20141222095321.GA21348@pox.localdomain> (raw)
In-Reply-To: <CACzMAJLtTKM57tD=COrZ5KOrZJVPVcUab=t2+y=CEU1e5xHV8g@mail.gmail.com>
Thanks a lot for sharing these minutes.
On 12/19/14 at 06:49pm, Andy Zhou wrote:
> Possible use cases of BPF in OVS Linux kernel datapath
> ===========================================
>
> [...]
>
> 4. Using BPF to implement overall OVS kernel module functionality
>
> Alexei likes this approach the most. The potential benefits are:
This would be my favourite as well long term assuming that the
performance benefits we hope for can be proven. A logical evolutionary
process might be 2, 3 and then go for the full coverage.
A small but: We can't just remove the existing Netlink based action
data path as non-OVS users exist which rely on it. So this would need
to exist in parallel unless we can get all users on board to transition
over to this new architecture.
prev parent reply other threads:[~2014-12-22 9:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-20 2:49 OVS + BPF, make sense? Andy Zhou
2014-12-22 9:53 ` Thomas Graf [this message]
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=20141222095321.GA21348@pox.localdomain \
--to=tgraf@noironetworks.com \
--cc=azhou@nicira.com \
--cc=dev@openvswitch.com \
--cc=netdev@vger.kernel.org \
/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