From: Thomas Monjalon <thomas@monjalon.net>
To: Kevin Laatz <kevin.laatz@intel.com>
Cc: web@dpdk.org, ferruh.yigit@intel.com, john.mcnamara@intel.com
Subject: Re: [dpdk-web] [PATCH v2] update 18.08 roadmap
Date: Thu, 14 Jun 2018 19:17:39 +0200 [thread overview]
Message-ID: <1819517.dFCtnLrurv@xps> (raw)
In-Reply-To: <20180612135841.31308-1-kevin.laatz@intel.com>
12/06/2018 15:58, Kevin Laatz:
> Signed-off-by: Kevin Laatz <kevin.laatz@intel.com>
Please add the link to the original announce in the commit log:
http://dpdk.org/ml/archives/dev/2018-June/103507.html
> + <li>allow setup/reconfiguration/tear down of queues at runtime
Should it be removed from this list? Already merged in 18.05?
> + <li>SoftNIC restructuring
You should add "Packet Framework" to describe above item
> + <li>Intel(r) QuickAssist Technology Compression PMD
Do we really need such "(r)" in our technical list?
> + <li>unified packet fragmentation
I would add "API" at the end, because it is not the fragmentation itself
which is unified ;)
> + <li>complete Intel PMD support for new descriptor status apis
Suggest: "complete support of new descriptor status API for Intel PMDs"
Thanks
next prev parent reply other threads:[~2018-06-14 17:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-06 15:01 [dpdk-web] [PATCH] " Kevin Laatz
2018-06-06 15:03 ` Mcnamara, John
2018-06-08 19:27 ` Mcnamara, John
2018-06-12 13:58 ` [dpdk-web] [PATCH v2] " Kevin Laatz
2018-06-14 9:01 ` Mcnamara, John
2018-06-14 17:17 ` Thomas Monjalon [this message]
2018-06-15 10:05 ` [dpdk-web] [PATCH v3] " Kevin Laatz
2018-06-15 10:44 ` Thomas Monjalon
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=1819517.dFCtnLrurv@xps \
--to=thomas@monjalon.net \
--cc=ferruh.yigit@intel.com \
--cc=john.mcnamara@intel.com \
--cc=kevin.laatz@intel.com \
--cc=web@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).