From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: "Mcnamara, John" <john.mcnamara@intel.com>
Cc: "Poole, James G" <james.g.poole@intel.com>,
"web@dpdk.org" <web@dpdk.org>,
"O'Driscoll, Tim" <tim.odriscoll@intel.com>
Subject: Re: [dpdk-web] [PATCH v2] roadmap: update to 16.11 roadmap
Date: Fri, 29 Jul 2016 15:11:08 +0200 [thread overview]
Message-ID: <2708208.fBWod0ToPL@xps13> (raw)
In-Reply-To: <B27915DBBA3421428155699D51E4CFE2025A9A24@IRSMSX103.ger.corp.intel.com>
2016-07-29 12:46, Mcnamara, John:
>
> > -----Original Message-----
> > From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com]
> > Sent: Wednesday, July 27, 2016 3:55 PM
> > To: Poole, James G <james.g.poole@intel.com>
> > Cc: web@dpdk.org; Mcnamara, John <john.mcnamara@intel.com>
> > Subject: Re: [dpdk-web] [PATCH v2] roadmap: update to 16.11 roadmap
> >
> > 2016-07-25 09:00, James Poole:
> > > <h3 id="1611">Version 16.11 (2016 November)</h3>
> > > <ul>
> > > - <li>Rx Filtering Rework
> > > - <li>QEMU Vhost backend Reconnect
> > > - <li>Delay Packet Copy in Vhost-user
> > > - <li>Fix library and symbol Namespace
> > > + <li>Additional Hardware and Software Crypto Algorithms</li>
> > > + <li>Cryptodev Performance Optimisation</li>
> > > + <li>Support for AES-GCM, AES-CTR, config file support to
> > remove hard-coding of SAs/SPs etc.</li>
> >
> > It is for IPsec example?
> >
> > > + <li>Use forward cipher function to generate IV on CBC
> > mode</li>
> >
> > Idem? is it really worth to be mentionned?
> >
> > > + <li>Generic Rx Filtering API</li>
> >
> > I think it is enough important to be in first position.
> >
> > > + <li>Optimize the Cuckoo Hash lookup stages by using
> > intelligent prefetching for keys and using IA AVX instructions for vector
> > processing of keys</li>
> >
> > Could it be shorter? "Optimize the Cuckoo Hash lookup for x86"?
> >
> > > + <li>vHost PMD xStats</li>
> > > + <li>Delay Packet Copy in vHost-User Dequeue</li>
>
> Hi Thomas,
>
> How about the following:
>
> * Add Generic Rx Filtering API
> * Extend Hardware and Software Crypto algorithms support
> * Cryptodev: Optimize performance
> * IPSec sample app: add support for AES-GCM, AES-CTR and configuration files
> * vHost PMD : Add support for XStats
> * vHost-User: Add delayed packet copy in dequeue
> * Cuckoo Hash: Optimize the lookup for x86
Looks good, thanks
prev parent reply other threads:[~2016-07-29 13:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-25 8:00 James Poole
2016-07-26 9:37 ` Mcnamara, John
2016-07-27 14:54 ` Thomas Monjalon
2016-07-29 12:46 ` Mcnamara, John
2016-07-29 13:11 ` Thomas Monjalon [this message]
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=2708208.fBWod0ToPL@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=james.g.poole@intel.com \
--cc=john.mcnamara@intel.com \
--cc=tim.odriscoll@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).