DPDK patches and discussions
 help / color / mirror / Atom feed
From: Jerin Jacob <jerin.jacob@caviumnetworks.com>
To: dev@dpdk.org
Cc: techboard@dpdk.org
Subject: [dpdk-dev] DPDK techboard minutes of August 30
Date: Wed, 6 Sep 2017 08:27:35 +0530	[thread overview]
Message-ID: <20170906025726.GA3617@jerin> (raw)

Hi all,

Here are the meeting notes for the last DPDK technical board meeting
held on 2017-08-30.

Attendees:
- Bruce Richardson
- Declan Doherty
- Hemant Agrawal
- Jan Blunck
- Jerin Jacob
- Konstantin Ananyev
- Keith Wiles
- Olivier Matz
- Stephen Hemminger
- Thomas Monjalon

1) A "dpdk-draft-ipsec" tree on dpdk.org has been approved for collaborating
the on going IPSec offload work. The committers details for this repo
is not yet finalized. Hemant will send the committer details after
discussing with interested parties.

2) The CLI discussion

Discussed the following aspects of CLI
a) Packaging
- The standalone library vs DPDK specific CLI library. Discussed the pros and cons
of both approaches. But not yet finalized on the particular scheme.
b) DPDK integration
- Removal or improve existing cmdline library vs a new CLI library. Not yet
finalized on this aspect. Keith submitted a presentation for the Dublin user-space summit on CLI.
- In order to complete the integration, The existing dpdk.org applications MUST
convert to use the new the CLI APIs
c) Git hosting
- A "dpdk-draft-cli" tree on dpdk.org has been approved for CLI work.

3) The policy for creating new draft trees on dpdk.org will be discussed at 
Dublin User space summit.

4) There was an agreement on bumping the HW requirement to treat similar to
ABI deprecation process. Bruce will send a patch to update the contributor's guide.

5) Next chair

In alphabetical order, Konstantin Ananyev will chair the next meeting.


Thanks,
Jerin

                 reply	other threads:[~2017-09-06  2:57 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=20170906025726.GA3617@jerin \
    --to=jerin.jacob@caviumnetworks.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).