From: Jerin Jacob <jerin.jacob@caviumnetworks.com>
To: dev@dpdk.org
Cc: techboard@dpdk.org
Subject: [dpdk-dev] Minutes of tech-board meeting 2018-1-17
Date: Mon, 22 Jan 2018 19:45:49 +0530 [thread overview]
Message-ID: <20180122141536.GA31199@jerin> (raw)
Date: 17 Jan 2018
Attendees:
Bruce Richardson,
Ferruh Yigit,
Hemant Agrawal,
Jerin Jacob,
Konstantin Ananyev,
Olivier Matz,
Thomas Monjalon
Yuanhan Liu
Absent:
Stephen Hemminger
Topic: Anatoly's request for discussing the DPDK dynamic memory allocation patches
* mail thread: http://dpdk.org/ml/archives/dev/2018-January/087029.html
* Since it is a significant change, it is planned to integrate early in v18.05 release.
* Request all interested parties to provide their initial comments before Jan 31.
Topic: Repository for compression work
* Tech board decided to give a next tree in dpdk.org for compression work.
* Next compression tree maintainer is not yet chosen. Tech board is looking forward
to getting a volunteer for next compression tree maintainership.
* Prefer to have an experienced dpdk contributor.
Next Meeting:
* 2018-01-31 @ 3pm UTC
* Konstantin to chair discussion as per alphabetical order
/Jerin
reply other threads:[~2018-01-22 14:16 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=20180122141536.GA31199@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).