From: Olga Shern <olgas@mellanox.com>
To: Thomas Monjalon <thomas@monjalon.net>, "web@dpdk.org" <web@dpdk.org>
Subject: Re: [dpdk-web] [PATCH] add Mellanox contributions to 17.08 roadmap
Date: Thu, 1 Jun 2017 19:08:43 +0000 [thread overview]
Message-ID: <DB6PR0501MB27575111C87FB576AEEA626DD3F60@DB6PR0501MB2757.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <20170531101455.31569-1-thomas@monjalon.net>
Acked-by: Olga Shern <olgas@mellanox.com>
> -----Original Message-----
> From: Thomas Monjalon [mailto:thomas@monjalon.net]
> Sent: Wednesday, May 31, 2017 1:15 PM
> To: web@dpdk.org
> Cc: Olga Shern <olgas@mellanox.com>
> Subject: [PATCH] add Mellanox contributions to 17.08 roadmap
>
> Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
> ---
> dev/roadmap.html | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/dev/roadmap.html b/dev/roadmap.html index 1618512..2636519
> 100644
> --- a/dev/roadmap.html
> +++ b/dev/roadmap.html
> @@ -46,8 +46,12 @@
> <li>Hotplug Notification
> <li>Vhost-user IOMMU support
> <li>Xen Netfront Driver
> + <li>Fail Safe driver
> <li>Enhance bnxt driver and update the HWRM version
> <li>Enic flow API support
> + <li>Interrupt Mode for mlx4 Rx
> + <li>RSS via Flow API for mlx5
> + <li>Optimized mlx5 data path for SSE
> <li>Generic Flow Enhancements for Intel drivers
> <li>Packet Type Recognition in ixgbe for SSE
> <li>NXP DPAA2 PMD Performance and Feature
> Enhancements @@ -55,6 +59,7 @@
> <li>NXP DPAA1 Bus, Mempool and PMD
> <li>ARM Architecture support in Atomic Rules Arkville Driver
> <li>VF Restore after PF Reset
> + <li>Isolated mode in Flow API
> <li>Generic QoS API
> <li>Generic Receive Offload
> <li>Cryptodev Multi-Core SW Scheduler
> --
> 2.13.0
prev parent reply other threads:[~2017-06-01 19:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-31 10:14 Thomas Monjalon
2017-06-01 9:25 ` Thomas Monjalon
2017-06-01 19:08 ` Olga Shern [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=DB6PR0501MB27575111C87FB576AEEA626DD3F60@DB6PR0501MB2757.eurprd05.prod.outlook.com \
--to=olgas@mellanox.com \
--cc=thomas@monjalon.net \
--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).