DPDK patches and discussions
 help / color / mirror / Atom feed
From: Olga Shern <olgas@mellanox.com>
To: "dev@dpdk.org" <dev@dpdk.org>, Thomas Monjalon <thomas@monjalon.net>
Cc: Erez Scop <erezsc@mellanox.com>, Shahaf Shuler <shahafs@mellanox.com>
Subject: [dpdk-dev] Mellanox Roadmap for 18.08
Date: Thu, 14 Jun 2018 07:28:43 +0000	[thread overview]
Message-ID: <VI1PR05MB457420458EAFD1FF6E0C09A5D37D0@VI1PR05MB4574.eurprd05.prod.outlook.com> (raw)

Hello all,

Mellanox Roadmap for 18.08 is the following:

Generic Flow API:

*         Adding actions for VLAN push/pop for flow API, implementation in mlx5 PMD enabling full HW offload.

*         Extending encapsulation API for MPLS tunnel type offload with ConnectX-5.

*         Extend flow pattern to match on metadata
mlx5 PMD:

*         support port representors (also known as "VF representors").

*         support RTE_FLOW_ACTION_TYPE_PORT_ID  action and PORT_ID flow item using full HW offload.

*         support VXLAN encap/decap for ConnectX-5 and BlueField SmartNIC.

*         support several flow priorities.

*         BlueField SmartNIC GA support, enabling running DPDK on SmartNIC ARM cores and/or Host cores with DPDK representors.

*         support 32bit compilation

*         Some enhancements for Multi-Packet Receive Queue.
mlx4 PMD

*         support TSO HW offload for ConnectX-3  Pro.

*         support 32bit compilation
TAP & FailSafe PMDs

*         support secondary-process in TAP and FailSafe PMDs.

*         Support TSO  for TAP PMD
Best Regards,
Olga

-------------------------------------------------------
Olga Shern
SW Sr. Director DPDK
Mellanox Technologies, Raanana, Israel

                 reply	other threads:[~2018-06-14  7:28 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=VI1PR05MB457420458EAFD1FF6E0C09A5D37D0@VI1PR05MB4574.eurprd05.prod.outlook.com \
    --to=olgas@mellanox.com \
    --cc=dev@dpdk.org \
    --cc=erezsc@mellanox.com \
    --cc=shahafs@mellanox.com \
    --cc=thomas@monjalon.net \
    /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).