From: Stephen Hemminger <stephen@networkplumber.org>
To: Hemant Agrawal <hemant.agrawal@nxp.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "techboard@dpdk.org" <techboard@dpdk.org>
Subject: Re: [dpdk-dev] DPDK techboard minutes @25-Mar-2020
Date: Mon, 6 Apr 2020 08:07:07 -0700 [thread overview]
Message-ID: <20200406080707.6175a648@hermes.lan> (raw)
In-Reply-To: <VI1PR0401MB2541551658714BAB872370D989C20@VI1PR0401MB2541.eurprd04.prod.outlook.com>
On Mon, 6 Apr 2020 06:08:23 +0000
Hemant Agrawal <hemant.agrawal@nxp.com> wrote:
> 2) How to share BPF with Linux
> The current DPDK BPF support is not complete and there are missing bits, which are DPDK specific. Specifically LD_INDIRECT/LD_ABSOLUTE and classic BPF to DPDK BPF converter are missing.
> The board agreed that we should try to work on creating shared code between DPDK and Linux. e.g eBPF verifier/jit etc.?
> In the past DPDK team has communicated with Linux BPF maintainers, there is an opportunity to talk with them again for possible collaboration.
> A.I. Konstantin will restart the discussion.
I have a CBF to eBPF prototype and would love to have collaboration on it.
prev parent reply other threads:[~2020-04-06 15:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-06 6:08 [dpdk-dev] DPDK techboard minutes @25-Mar-2020 Hemant Agrawal
2020-04-06 15:07 ` 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=20200406080707.6175a648@hermes.lan \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.com \
--cc=techboard@dpdk.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 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.