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]  [dpdk-techboard] next techboard meeting (15th, September)
Date: Tue, 12 Sep 2017 09:12:46 +0000	[thread overview]
Message-ID: <2601191342CEEE43887BDE71AB9772584F249DBE@irsmsx105.ger.corp.intel.com> (raw)


Hi everyone,

The next meeting of the tech board will happen on IRC #dpdk-board, at 2pm UTC, on 15th of September(Friday)

Agenda:
1) Discussion on Thomas proposal to nominate Ferruh as committer to the main tree
and add more sub-trees
http://dpdk.org/ml/archives/dev/2017-September/075094.html

2) Discussion on New RFC:
a) ethdev new offload API
http://dpdk.org/ml/archives/dev/2017-August/072643.html
b) IPSec offload(rte_security)
http://dpdk.org/ml/archives/dev/2017-August/072900.html
c) event timer wheel
http://dpdk.org/ml/archives/dev/2017-August/072980.htm
d) membership library
http://dpdk.org/ml/archives/dev/2017-September/074187.html

3) Request to create the dpdk-next-packet-framework git tree
from Dumitrescu, Cristian <cristian.dumitrescu@intel.com>

4) Request for feedback regarding the new license requirement for the
optimized version of 64bit division code from libdivide.
from  Pavan Nikhilesh Bhagavatula <pbhagavatula@caviumnetworks.com> 
http://dpdk.org/ml/archives/dev/2017-September/074705.html
http://dpdk.org/ml/archives/dev/2017-September/074759.html

Online version of agenda:
https://annuel.framapad.org/p/dpdk-techboard-agenda

                 reply	other threads:[~2017-09-12  9:12 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=2601191342CEEE43887BDE71AB9772584F249DBE@irsmsx105.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).