From: Jerin Jacob <jerin.jacob@caviumnetworks.com>
To: techboard@dpdk.org
Cc: dev@dpdk.org
Subject: [dpdk-dev] [dpdk-techboard] next techboard meeting (29th, August)
Date: Sun, 27 Aug 2017 18:54:35 +0530 [thread overview]
Message-ID: <20170827132425.GA11627@jerin> (raw)
Hi All,
The next meeting of the tech board will happen on IRC #dpdk-board, at 3pm UTC, on 29th of August(Tuesday)
Agenda:
1) Discussion on next tree requests
a) Next tree for IPSec offload and maintainership
http://dpdk.org/ml/archives/dev/2017-August/072995.html
b) Next tree for cli
http://dpdk.org/ml/archives/dev/2017-August/073343.html
2) Approval of a policy for changes to the minimum DPDK requirements.
e.g. like what was done with bumping IA min to SSE4.2 in last release.
3) 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.html
Online version of agenda:
https://annuel.framapad.org/p/dpdk-techboard-aug-29
next reply other threads:[~2017-08-27 13:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-27 13:24 Jerin Jacob [this message]
2017-08-28 15:04 ` Bruce Richardson
2017-08-29 15:30 ` Jerin Jacob
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=20170827132425.GA11627@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).