DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@amd.com>
To: shaibran@amazon.com
Cc: dev@dpdk.org, rbeider@amazon.com, atrwajee@amazon.com,
	amitbern@amazon.com
Subject: Re: [PATCH v3 0/5] net/ena: v2.8.0 driver release
Date: Fri, 27 Oct 2023 17:33:29 +0100	[thread overview]
Message-ID: <0c26b5dc-34e1-4349-a38a-511561365ab7@amd.com> (raw)
In-Reply-To: <20231026142135.19967-1-shaibran@amazon.com>

On 10/26/2023 3:21 PM, shaibran@amazon.com wrote:
> From: Shai Brandes <shaibran@amazon.com>
> 
> Hi,
> 
> This patchset contains alignment of the driver to the latest HAL version
> which adds support for retrieving new metrics from the device and opens
> a path to use additional device features that are not yet supported by
> the driver.
> 
> The new driver features are mostly about adding additional metrics.
> We added support for an additional customer metric, ENA-express metrics
> and are now reporting also rx overrun errors. All new metrics have MP
> support.
> 
> * Testing:
> The team performed directed tests for all the features and executed our
> proprietary performance benchamarking (BW, PPS, Latency) to verify there
> is no regression. It was executed on the entire Amazon EC2 instance types
> matrix that covers all device generations and CPU architectures. 
> 
> ---
> v3:
> * updated the ena hal upgrade patch 0001:
>   * Removed all irrelvant headers from the ena_plat
>   * Changed interal bit shift implementation to rte define.
>   * Fixed an unintentional revert of queue status patch.
>   * Fixed minor typo errors.
>   * moved the ena release notes section to its proper location
>     in the release notes doc (ordered in vendor in the driver group).
> 
> v2:
> * Fixed spelling issues from checkpatch in patch 0001
> 
> Shai Brandes (5):
>   net/ena: hal upgrade
>   net/ena: add support for connection tracking metric
>   net/ena: report Rx overrun errors in xstats
>   net/ena: add support for ena-express metrics
>   net/ena: update ena version to 2.8.0
>

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

      parent reply	other threads:[~2023-10-27 16:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-26 14:21 shaibran
2023-10-26 14:21 ` [PATCH v3 1/5] net/ena: hal upgrade shaibran
2023-10-26 14:21 ` [PATCH v3 2/5] net/ena: add support for connection tracking metric shaibran
2023-10-26 14:21 ` [PATCH v3 3/5] net/ena: report Rx overrun errors in xstats shaibran
2023-10-26 14:21 ` [PATCH v3 4/5] net/ena: add support for ena-express metrics shaibran
2023-10-26 14:21 ` [PATCH v3 5/5] net/ena: update ena version to 2.8.0 shaibran
2023-10-27 16:33 ` 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=0c26b5dc-34e1-4349-a38a-511561365ab7@amd.com \
    --to=ferruh.yigit@amd.com \
    --cc=amitbern@amazon.com \
    --cc=atrwajee@amazon.com \
    --cc=dev@dpdk.org \
    --cc=rbeider@amazon.com \
    --cc=shaibran@amazon.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).