DPDK patches and discussions
 help / color / mirror / Atom feed
From: Hemant Agrawal <hemant.agrawal@nxp.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Cc: "techboard@dpdk.org" <techboard@dpdk.org>
Subject: [dpdk-dev] DPDK techboard minutes @25-Mar-2020
Date: Mon, 6 Apr 2020 06:08:23 +0000	[thread overview]
Message-ID: <VI1PR0401MB2541551658714BAB872370D989C20@VI1PR0401MB2541.eurprd04.prod.outlook.com> (raw)

Minutes of Technical Board Meeting, 25-Mar-2020

Members Attending
-----------------
-Bruce
-Hemant (Chair)
-Honnappa
-Jerin
-Kevin
-Konstantin
-Maxime
-Olivier
-Stephen
-Thomas

NOTE: The technical board meetings every second Wednesday on IRC channel  #dpdk-board, at 3pm UTC. Meetings are public and DPDK community members are welcome to attend.

NOTE: Next meeting will be on Wednesday 2020-04-08 @3pm UTC, and will be chaired by Ferruh

1) Kubernetes integration status request raised by Trishan - blog post?
              Maxime will look into it. He is currently busy. 

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. 

3. IF proxy library introduction:
       http://patches.dpdk.org/cover/66503/
	It was discussed and agreed that there is a need to have a common mechanism to allow the user configuration to be passed to the DPDK app and better integration with Linux devices in DPDK and in common place.
	Next step is to review the proposed design and implementation in the mailing list.
	There was a suggestion that instead of creating a new app for if proxy, it should be integrated into L3fwd sample application. However it shall not cause perf drop.

4. Adding new apps and examples
              If new apps/examples are demonstrating new functionality and uses of APIs, which is not covered elsewhere. they will be ok The reviewers should suggest alternatives if the example functions should be built into an existing example.

	Any addition to app folder should be restricted to testing and CI purposes.
   
5. CfP for Bordeaux is open but not officially announced for now
 
      https://events.linuxfoundation.org/dpdk-userspace-summit/

             reply	other threads:[~2020-04-06  6:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-06  6:08 Hemant Agrawal [this message]
2020-04-06 15:07 ` Stephen Hemminger

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=VI1PR0401MB2541551658714BAB872370D989C20@VI1PR0401MB2541.eurprd04.prod.outlook.com \
    --to=hemant.agrawal@nxp.com \
    --cc=dev@dpdk.org \
    --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 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).