From: Thomas Monjalon <thomas@monjalon.net>
To: Brian Archbold <brian.archbold@intel.com>
Cc: web@dpdk.org
Subject: Re: [dpdk-web] [PATCH v2] update roadmap for 18.05
Date: Thu, 08 Mar 2018 23:25:32 +0100 [thread overview]
Message-ID: <2933639.xypejkkKWr@xps> (raw)
In-Reply-To: <20180228085104.2665-1-brian.archbold@intel.com>
Hi,
28/02/2018 09:51, Brian Archbold:
> Signed-off-by: Brian Archbold <brian.archbold@intel.com>
> ---
> <h3 id="1805">Version 18.05 (2018 May)</h3>
> <ul>
> - <li>memory management rework
> - <li>hotplug
> - <li>new device specification (devargs) syntax
> - <li>secondary process support in virtual devices
> - <li>ethdev port representor driver
> - <li>ARM support for ark
> - <li>mlx5 IPsec offload
> - <li>virtio-crypto driver
> - <li>eventdev ordered and atomic queues for DPAA2
> - <li>eventdev crypto adapter
> - <li>libedit integration
> + <li>selective datapath in the vhost-user library
> + <li>new Intel device driver (IFC VF) for accelerated virtio data path
> + <li>interrupt mode for vhost
> + <li>virtio-user for virtio-crypto
> + <li>ethdev API to for recommended descriptor ring sizes
> + <li>memory subsystem improvements
> + <li>ip pipeline enhancements
> + <li>new API to support hardware and software compression and decompression
> + <li>new API to manage tunnel endpoints
> + <li>port representor, a virtual PMD with a logical representation of any port
> + <li>add PPPoE/PPPoL2Tv2 to I40e PMD
> + <li>update Intel PMDs for Rx/Tx offload APIs
> + <li>uevent support for hotplug
This patch is removing all to replace it by Intel list.
Instead of asking a new patch, I have applied and fixed it.
prev parent reply other threads:[~2018-03-08 22:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-28 8:51 Brian Archbold
2018-03-01 9:44 ` Mcnamara, John
2018-03-08 22:25 ` 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=2933639.xypejkkKWr@xps \
--to=thomas@monjalon.net \
--cc=brian.archbold@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).