DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ajit Khaparde <ajit.khaparde@broadcom.com>
To: dpdk-dev <dev@dpdk.org>
Cc: Thomas Monjalon <thomas@monjalon.net>
Subject: [dpdk-dev] Broadcom roadmap for DPDK 20.08 release
Date: Fri, 5 Jun 2020 21:17:51 -0700	[thread overview]
Message-ID: <CACZ4nhuDBHOxHyDeg7y2NfFRKMtucq1c5wev1fyXFvHtT8frSA@mail.gmail.com> (raw)

The following is Broadcom's roadmap for DPDK 20.08:

* Add support for VF representors
* Add support for flow counters: RTE_FLOW_ACTION_TYPE_COUNT

* Add support for VLAN pop/push: RTE_FLOW_ACTION_TYPE_OF_POP(PUSH)_VLAN
* Add support for VXLAN encap/decap: RTE_FLOW_ACTION_TYPE_VXLAN_ENCAP(DECAP)
* Add support for L2 rewrite: RTE_FLOW_ACTION_TYPE_SET_MAC_SRC(DST)
* Add support for L3 rewrite: RTE_FLOW_ACTION_TYPE_SET_IPV4(IPV6)_SRC(DST)
* Add support for L4 rewrite: RTE_FLOW_ACTION_TYPE_SET_TP_SRC(DST)
* Add support for TTL decrement: RTE_FLOW_ACTION_TYPE_DEC_TTL
* Add support for rx_burst_mode_get and tx_burst_mode_get
* Add support for multi-device infrastructure
     - resource management, flow table, device-specific template flows
* Add vector mode support for ARM CPUs

                 reply	other threads:[~2020-06-06  4:18 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=CACZ4nhuDBHOxHyDeg7y2NfFRKMtucq1c5wev1fyXFvHtT8frSA@mail.gmail.com \
    --to=ajit.khaparde@broadcom.com \
    --cc=dev@dpdk.org \
    --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).