DPDK patches and discussions
 help / color / mirror / Atom feed
From: Gagandeep Singh <G.Singh@nxp.com>
To: Hemant Agrawal <hemant.agrawal@nxp.com>,
	"ferruh.yigit@intel.com" <ferruh.yigit@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 00/10] net/enetc: optimization and cleanup
Date: Tue, 3 Mar 2020 12:31:22 +0000	[thread overview]
Message-ID: <AM7PR04MB69844E234C00467DC75DD495E1E40@AM7PR04MB6984.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <20200302143209.11854-1-hemant.agrawal@nxp.com>



> -----Original Message-----
> From: Hemant Agrawal <hemant.agrawal@nxp.com>
> Sent: Monday, March 2, 2020 8:02 PM
> To: ferruh.yigit@intel.com
> Cc: dev@dpdk.org; Gagandeep Singh <G.Singh@nxp.com>
> Subject: [PATCH 00/10] net/enetc: optimization and cleanup
> 
> This patch series includes patches to optimize and clean
> the network driver for ENETC
> 
> Alex Marginean (10):
>   net/enetc: do not stall in clean Tx ring
>   net/enetc: use relaxed read for Tx CI in clean Tx
>   net/enetc: batch process enetc clean Tx ring calls
>   net/enetc: erratum wa for Rx lock-up issue
>   net/enetc: improve batching Rx ring refill
>   net/enetc: cache align enetc bdr structure
>   net/enetc: use bulk alloc in Rx refill ring
>   net/enetc: use bulk free in Tx clean
>   net/enetc: improve prefetch in Rx ring clean
>   net/enetc: init SI transactions attribute reg
> 
>  drivers/net/enetc/Makefile        |   1 +
>  drivers/net/enetc/base/enetc_hw.h |   5 +-
>  drivers/net/enetc/enetc.h         |  10 +--
>  drivers/net/enetc/enetc_ethdev.c  |  11 ++-
>  drivers/net/enetc/enetc_rxtx.c    | 131 +++++++++++++++++++++++-------
>  drivers/net/enetc/meson.build     |   1 +
>  6 files changed, 123 insertions(+), 36 deletions(-)
> 

Series-acked-by:  Gagandeep Singh <g.singh@nxp.com>

> --
> 2.17.1


  parent reply	other threads:[~2020-03-03 12:31 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-02 14:31 Hemant Agrawal
2020-03-02 14:32 ` [dpdk-dev] [PATCH 01/10] net/enetc: do not stall in clean Tx ring Hemant Agrawal
2020-03-02 14:32 ` [dpdk-dev] [PATCH 02/10] net/enetc: use relaxed read for Tx CI in clean Tx Hemant Agrawal
2020-03-02 14:32 ` [dpdk-dev] [PATCH 03/10] net/enetc: batch process enetc clean Tx ring calls Hemant Agrawal
2020-03-02 14:32 ` [dpdk-dev] [PATCH 04/10] net/enetc: erratum wa for Rx lock-up issue Hemant Agrawal
2020-03-02 14:32 ` [dpdk-dev] [PATCH 05/10] net/enetc: improve batching Rx ring refill Hemant Agrawal
2020-03-02 14:32 ` [dpdk-dev] [PATCH 06/10] net/enetc: cache align enetc bdr structure Hemant Agrawal
2020-03-02 14:32 ` [dpdk-dev] [PATCH 07/10] net/enetc: use bulk alloc in Rx refill ring Hemant Agrawal
2020-03-02 14:32 ` [dpdk-dev] [PATCH 08/10] net/enetc: use bulk free in Tx clean Hemant Agrawal
2020-03-02 14:32 ` [dpdk-dev] [PATCH 09/10] net/enetc: improve prefetch in Rx ring clean Hemant Agrawal
2020-03-02 14:32 ` [dpdk-dev] [PATCH 10/10] net/enetc: init SI transactions attribute reg Hemant Agrawal
2020-03-03 12:31 ` Gagandeep Singh [this message]
2020-03-03 14:02   ` [dpdk-dev] [PATCH 00/10] net/enetc: optimization and cleanup Ferruh Yigit

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=AM7PR04MB69844E234C00467DC75DD495E1E40@AM7PR04MB6984.eurprd04.prod.outlook.com \
    --to=g.singh@nxp.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=hemant.agrawal@nxp.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).