DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Ananyev, Konstantin" <konstantin.ananyev@intel.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Cc: "techboard@dpdk.org" <techboard@dpdk.org>
Subject: [dpdk-dev] Minutes of tech-board meeting 2017-03-20
Date: Thu, 23 Mar 2017 10:48:52 +0000	[thread overview]
Message-ID: <2601191342CEEE43887BDE71AB9772583FAD3EB8@IRSMSX109.ger.corp.intel.com> (raw)

Hi,

Below are the minutes of the last DPDK technical board meeting that occurred at 2017-03-20.

Please note that meetings are open to all to attend.
The next meeting is planned for the first week of April, any topics to be referred
to the tech board for discussion at that meeting should be emailed to techboard@dpdk.org
by March 31th at the latest.

Member attendees:

- Bruce Richardson
- Hemant Agrawal
- Jan Blunck
- Jerin Jacob
- Konstantin Ananyev
- Olivier Matz
- Stephen Hemminger
- Thomas Monjalon
- Yuanhan Liu

1. General Meeting Admin
--------------------------------

 Jerin Jacob volunteered to chair the next meeting.

 No particular date was agreed for next meeting (proposed 3/5th of April 3PM UTC).

 Jerin to follow on mail to select a date/time and send a reminder with agenda a few days in advance.

2. AVP PMD
---------------

TB has no major concerns about AVP PMD to be up-streamed into dpdk.org.
TB recommends  to provide a good documentation introduction for the AVP PMD and its scope.
It should be clearly stated  that right now AVP PMD is limited to use with WindRiver hypervisor
and for most cases virtio is still a preferred virtual device to use with QEMU.

3. Failsafe PMD
-------------------

TB recommendation:
 - For 17.05 try to implement hotplug support at EAL level
-  For 17.08 reconsider failsafe mode.

4. PRGDEV
-------------

TB opinion is that it is not ready for inclusion right now.
The exact requirements should be clearly described, so any member can participate
in the discussion and propose other ways to achieve the same goal.
TB also recommends to include some good use case(s) into the proposal.

5. Traffic management (Hierarchical QoS scheduler)
---------------------------------------------------------------

Include into next-tree with Cristian Dumitrescu as a maintainer .
Target release to merge into dpdk.org mainline: 17.08.
Gating condition: 1+ HW device support.
 
6. Divergence between DPDK/Linux PF/VF implementations
------------------------------------------------------------------------

Discussion postponed until next TB meeting.

                 reply	other threads:[~2017-03-23 10:48 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:
  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=2601191342CEEE43887BDE71AB9772583FAD3EB8@IRSMSX109.ger.corp.intel.com \
    --to=konstantin.ananyev@intel.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).