DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Michal Krawczyk <mk@semihalf.com>, dev@dpdk.org
Cc: gtzalik@dpdk.org, mw@dpdk.org, matua@amazon.com, rk@semihalf.com
Subject: Re: [dpdk-dev] [PATCH 00/20] net/ena: ENAv2 release
Date: Tue, 18 Dec 2018 17:18:35 +0000	[thread overview]
Message-ID: <f6072377-d823-e836-ae0b-7798209b18f5@intel.com> (raw)
In-Reply-To: <20181214131846.22439-1-mk@semihalf.com>

On 12/14/2018 1:18 PM, Michal Krawczyk wrote:
> Hi,
> 
> we are proud to announce ENAv2 driver for the DPDK.
> It is already available for the Linux, and now also ENAv2 can be used with
> DPDK on the appropriate AWS instances.
> 
> To summarize, this release contains:
> 
> **New major features**
>   * LLQv2 which is Low Latency Queue v2. This feature reduces the latency
>     of the packets by pushing the header directly through the PCI to the
>     device, before the DMA is even triggered. This allows the NIC to
>     asynchronously prepare for the next incoming packet, when the DMA will
>     be finished.
>   * Independent configuration of HW Tx and Rx ring depths. Also, on some
>     instances it is possible to create 8k Rx descriptors per ring.
>   * Additional doorbell check on Tx, to handle Tx more efficiently for big
>     bursts of packets
>   * Per queue statistics
>   * Extended statistics using xstats DPDK API
> 
> **New major bug fixes**
>   * The reset routine was aligned with the DPDK API, so now it can be
>     handled as in other PMDs
>   * Fixes for OOO completion
>   * Fixes for memory leaks due to port stops and starts in the middle of
>     traffic
> 
> There are also minor bug fixes and features in addition to the ones
> mentioned above.
> 
> Michal Krawczyk (4):
>   net/ena: add LLQv2 support
>   net/ena: add per-queue software counters stats
>   docs: update ENA PMD documentation and features
>   net/ena: release of the ENAv2 driver (v2.0.0)
> 
> Rafal Kozik (15):
>   net/ena: update ena_com for the ENAv2
>   net/ena: pass number of CPUs to the host info structure
>   net/ena: add reset reason in rx error
>   net/ena: add hw queues depth setup
>   net/ena: skip packet with wrong req_id
>   net/ena: increase maximum Rx ring size
>   net/ena: call additional doorbells if needed
>   net/ena: destroy queues if start failed
>   net/ena: reset should not reconfigure queues
>   net/ena: adjust new line in log messages
>   net/ena: add supported RSS offloads types
>   net/ena: fix invalid reference to variable in union
>   net/ena: fix cleanup for out of order packets
>   net/ena: new way of getting rx drops
>   net/ena: update completion queue after cleanup
> 
> Solganik Alexander (1):
>   net/ena: expose ENA-specific statistics in extended stats

Series applied to dpdk-next-net/master, thanks.

(v3 of 14/20 used, for rest it is v1)

      parent reply	other threads:[~2018-12-18 17:18 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-14 13:18 Michal Krawczyk
2018-12-14 13:18 ` [dpdk-dev] [PATCH 01/20] net/ena: update ena_com for the ENAv2 Michal Krawczyk
2018-12-14 13:18 ` [dpdk-dev] [PATCH 02/20] net/ena: pass number of CPUs to the host info structure Michal Krawczyk
2018-12-14 13:18 ` [dpdk-dev] [PATCH 03/20] net/ena: add reset reason in rx error Michal Krawczyk
2018-12-14 13:18 ` [dpdk-dev] [PATCH 04/20] net/ena: add hw queues depth setup Michal Krawczyk
2018-12-14 13:18 ` [dpdk-dev] [PATCH 05/20] net/ena: skip packet with wrong req_id Michal Krawczyk
2018-12-14 13:18 ` [dpdk-dev] [PATCH 06/20] net/ena: add LLQv2 support Michal Krawczyk
2018-12-14 13:18 ` [dpdk-dev] [PATCH 07/20] net/ena: increase maximum Rx ring size Michal Krawczyk
2018-12-14 13:18 ` [dpdk-dev] [PATCH 08/20] net/ena: call additional doorbells if needed Michal Krawczyk
2018-12-14 13:18 ` [dpdk-dev] [PATCH 09/20] net/ena: destroy queues if start failed Michal Krawczyk
2018-12-14 13:18 ` [dpdk-dev] [PATCH 10/20] net/ena: reset should not reconfigure queues Michal Krawczyk
2018-12-14 13:18 ` [dpdk-dev] [PATCH 11/20] net/ena: adjust new line in log messages Michal Krawczyk
2018-12-14 13:18 ` [dpdk-dev] [PATCH 12/20] net/ena: add supported RSS offloads types Michal Krawczyk
2018-12-14 13:18 ` [dpdk-dev] [PATCH 13/20] net/ena: fix invalid reference to variable in union Michal Krawczyk
2018-12-14 13:18 ` [dpdk-dev] [PATCH 14/20] net/ena: fix cleanup for out of order packets Michal Krawczyk
2018-12-14 13:18 ` [dpdk-dev] [PATCH 15/20] net/ena: add per-queue software counters stats Michal Krawczyk
2018-12-14 13:18 ` [dpdk-dev] [PATCH 16/20] net/ena: expose ENA-specific statistics in extended stats Michal Krawczyk
2018-12-14 13:18 ` [dpdk-dev] [PATCH 17/20] net/ena: new way of getting rx drops Michal Krawczyk
2018-12-14 13:18 ` [dpdk-dev] [PATCH 18/20] net/ena: update completion queue after cleanup Michal Krawczyk
2018-12-14 13:18 ` [dpdk-dev] [PATCH 19/20] docs: update ENA PMD documentation and features Michal Krawczyk
2018-12-14 13:18 ` [dpdk-dev] [PATCH 20/20] net/ena: release of the ENAv2 driver (v2.0.0) Michal Krawczyk
2018-12-17 11:03 ` [dpdk-dev] [PATCH v2 14/20] net/ena: fix cleanup for out of order packets Michal Krawczyk
2018-12-17 11:06   ` [dpdk-dev] [PATCH v3 " Michal Krawczyk
2018-12-18 17:18 ` Ferruh Yigit [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=f6072377-d823-e836-ae0b-7798209b18f5@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=dev@dpdk.org \
    --cc=gtzalik@dpdk.org \
    --cc=matua@amazon.com \
    --cc=mk@semihalf.com \
    --cc=mw@dpdk.org \
    --cc=rk@semihalf.com \
    /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).