DPDK community structure changes
 help / color / mirror / Atom feed
From: "O'Driscoll, Tim" <tim.odriscoll@intel.com>
To: "moving@dpdk.org" <moving@dpdk.org>
Subject: [dpdk-moving] Minutes from "Moving DPDK to Linux Foundation" call, February 14th
Date: Thu, 16 Feb 2017 12:15:39 +0000
Message-ID: <26FA93C7ED1EAA44AB77D62FBE1D27BA722BE7D8@IRSMSX108.ger.corp.intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 4696 bytes --]

Here are my notes from yesterday's call. Please feel free to correct any errors or to add additional details.

Attendees: Bruce Richardson (Intel), Erez Scop (Mellanox), George Zhao (Huawei), Jan Blunck (Brocade), Jaswinder Singh (NXP), Jim St. Leger (Intel), John Bromhead (Cavium), John McNamara (Intel), Keith Wiles (Intel), Kevin Traynor (Red Hat), Thomas Monjalon (6WIND), Tim O'Driscoll (Intel), Vincent Jardin (6WIND).

Firstly, here are some links to help keep track of things:

Project Charter: https://docs.google.com/document/d/1x43ycfW3arJNX-e6NQt3OVzAuNXtD7dppIhrY48FoGs

Budget estimate: https://docs.google.com/spreadsheets/d/1-3686Xb_jf4FtxdX8Mus9UwIxUb2vI_ppmJV5GnXcLg/edit#gid=302618256

Reference Lab Proposal: http://dpdk.org/ml/archives/moving/2017-February/000177.html

Technical governance, including info on Maintainers and sub-trees: http://dpdk.org/doc/guides/contributing/index.html & http://dpdk.org/dev.

Summary of discussion at Userspace event in Dublin: http://dpdk.org/ml/archives/dev/2016-October/049259.html

Minutes of January 10th call: http://dpdk.org/ml/archives/moving/2017-January/000136.html

Minutes of January 17th call: http://dpdk.org/ml/archives/moving/2017-January/000157.html

Minutes of January 24th call: http://dpdk.org/ml/archives/moving/2017-January/000162.html

Minutes of January 31st call: http://dpdk.org/ml/archives/moving/2017-February/000176.html

Minutes of February 7th call: http://dpdk.org/ml/archives/moving/2017-February/000179.html

Open Reference Lab:

- Agreed that an Open Reference Lab is a good idea. It would help to identify performance issues and would improve quality and stability.

- We discussed whether all performance numbers should be made public. It was felt that there may be cases where some vendors do not want absolute numbers published, and that in those cases we could publish delta numbers to show the difference between one performance test and another. This could happen in cases where DPDK is being supported on a new platform (e.g. as is happening now with NXP) and performance has not yet reached the expected level. This would just be a temporary situation until performance tuning is complete. Thomas suggested that we give each vendor the option, and let them decide when they're ready to publish absolute numbers.

- Agreed that the lab should be referred to as the Open Reference Lab.

- Agreed that the scope is to identify performance regression, not to performance test new features and/or new hardware. Vendors will still want to performance test DPDK on their latest hardware, but that should be done internally in their own labs.

- Discussed the frequency of testing. Ideally this would be done per patch so that we know the performance impacts of each patch and can take that into account when agreeing whether the patch should be accepted into DPDK. Testing per patch will increase the resource requirements, so we'll need to take that into account.

- Discussed how we want to maintain the lab. This is related to the decision on where we want to host it. Ideally, it should be administered by people familiar with DPDK and familiar with the hardware.

- Jan suggested looking at how other projects have handled admin for open labs. We'll look into this.

- Agreed that it would be useful to allow people to submit software applications to be run in the lab, as Matt suggested in a previous discussion. This will add some complexity.

- Discussed how we ensure that the lab doesn't become a competitive environment for vendors to show that their performance is the best. We need to agree some rules to prevent this.

- We need to look at hosting options (not just the LF, but other options too). To do this, we need to know hardware and power requirements. We haven't got to that level of detail yet.

- We'll discuss further in a smaller group. Anybody interested in participating in those discussions should let me know.

Tech Board:

- A tech board meeting was held yesterday. Minutes will be published. Making tech board meetings public was one of the agenda items.

Next Meeting:

Tuesday February 21st at 3pm GMT, 4pm CET, 10am EST, 7am PST. Access numbers for the call are:

  Skype meeting: https://meet.intel.com/tim.odriscoll/97F0Q1HF

  France: +33 1588 77298

  UK: +44 179340 2663

  USA: +1 916 356 2663

  Bridge Number: 5

  Conference ID: 120705852

We need to discuss how membership discussions are progressing and if our target date of a project launch to coincide with ONS (http://events.linuxfoundation.org/events/open-networking-summit, April 3-6) is realistic.

[-- Attachment #2: Type: text/html, Size: 9439 bytes --]

                 reply	other threads:[~2017-02-16 12:15 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=26FA93C7ED1EAA44AB77D62FBE1D27BA722BE7D8@IRSMSX108.ger.corp.intel.com \
    --to=tim.odriscoll@intel.com \
    --cc=moving@dpdk.org \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

DPDK community structure changes

This inbox may be cloned and mirrored by anyone:

	git clone --mirror http://inbox.dpdk.org/moving/0 moving/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 moving moving/ http://inbox.dpdk.org/moving \
	public-inbox-index moving

Example config snippet for mirrors.
Newsgroup available over NNTP:

AGPL code for this site: git clone https://public-inbox.org/public-inbox.git