From: Stephen Hemminger <stephen@networkplumber.org>
To: Anupam Kapoor <anupam.kapoor@gmail.com>
Cc: Gal Sagie <gal.sagie@gmail.com>, "<dev@dpdk.org>" <dev@dpdk.org>
Subject: Re: [dpdk-dev] ebpf support in dpdk
Date: Fri, 21 Apr 2017 10:17:21 -0700 [thread overview]
Message-ID: <20170421101721.6b9e3bd9@xeon-e3> (raw)
In-Reply-To: <CAEXHiZGdck2isofr4DO0TyFEm9egDbund0S+HrpWSXHAYc27mg@mail.gmail.com>
On Fri, 21 Apr 2017 17:23:13 +0530
Anupam Kapoor <anupam.kapoor@gmail.com> wrote:
> On Fri, Apr 21, 2017 at 5:18 PM, Gal Sagie <gal.sagie@gmail.com> wrote:
>
> > I have a feeling you are talking about P4....
>
>
> well, not p4, but more specifically 'protocol-oblivious-forwarding' (POF).
> ebpf can describe both match+action rules on dpdk...
>
> --
> kind regards
> anupam
>
> In the beginning was the lambda, and the lambda was with Emacs, and Emacs
> was the lambda.
There is already a userspace eBPF library, why does DPDK have to (re)invent everything?
https://github.com/tuxology/libebpf
prev parent reply other threads:[~2017-04-21 17:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-21 10:32 Anupam Kapoor
2017-04-21 11:48 ` Gal Sagie
2017-04-21 11:53 ` Anupam Kapoor
2017-04-21 17:17 ` Stephen Hemminger [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=20170421101721.6b9e3bd9@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=anupam.kapoor@gmail.com \
--cc=dev@dpdk.org \
--cc=gal.sagie@gmail.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).