DPDK patches and discussions
 help / color / mirror / Atom feed
From: Raslan Darawsheh <rasland@nvidia.com>
To: Alexander Kozyrev <akozyrev@nvidia.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: Slava Ovsiienko <viacheslavo@nvidia.com>, Matan Azrad <matan@nvidia.com>
Subject: RE: [PATCH 0/5] net/mlx5: enhanced CQE compression layout
Date: Tue, 7 Mar 2023 09:03:31 +0000	[thread overview]
Message-ID: <BYAPR12MB3078E8A16AD6769DDB47B3ACCFB79@BYAPR12MB3078.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20230228164310.807594-1-akozyrev@nvidia.com>

Hi,

> -----Original Message-----
> From: Alexander Kozyrev <akozyrev@nvidia.com>
> Sent: Tuesday, February 28, 2023 6:43 PM
> To: dev@dpdk.org
> Cc: Raslan Darawsheh <rasland@nvidia.com>; Slava Ovsiienko
> <viacheslavo@nvidia.com>; Matan Azrad <matan@nvidia.com>
> Subject: [PATCH 0/5] net/mlx5: enhanced CQE compression layout
> 
> Support Enhanced CQE Compression Layout in mlx5 driver for better latency
> and SW utilization.
> 
> Alexander Kozyrev (5):
>   common/mlx5: detect enhanced CQE compression capability
>   common/mlx5: add CQE validity iteration count
>   net/mlx5: support enhanced CQE compression in Rx burst
>   net/mlx5: support enhanced CQE zipping in vector Rx burst
>   net/mlx5: enable enhanced CQE compression
> 
>  doc/guides/nics/mlx5.rst                 |  14 +-
>  doc/guides/rel_notes/release_23_03.rst   |   1 +
>  drivers/common/mlx5/mlx5_common.h        |  57 +++++++-
>  drivers/common/mlx5/mlx5_common_devx.c   |   4 +-
>  drivers/common/mlx5/mlx5_devx_cmds.c     |   3 +
>  drivers/common/mlx5/mlx5_devx_cmds.h     |   2 +
>  drivers/common/mlx5/mlx5_prm.h           |  42 ++++--
>  drivers/net/mlx5/mlx5.c                  |  17 ++-
>  drivers/net/mlx5/mlx5.h                  |   1 +
>  drivers/net/mlx5/mlx5_devx.c             |   2 +
>  drivers/net/mlx5/mlx5_rx.c               | 175 +++++++++++++++--------
>  drivers/net/mlx5/mlx5_rx.h               |  13 +-
>  drivers/net/mlx5/mlx5_rxq.c              |   5 +-
>  drivers/net/mlx5/mlx5_rxtx_vec.c         |  24 +++-
>  drivers/net/mlx5/mlx5_rxtx_vec_altivec.h | 108 ++++++++++----
>  drivers/net/mlx5/mlx5_rxtx_vec_neon.h    |  91 ++++++++----
>  drivers/net/mlx5/mlx5_rxtx_vec_sse.h     |  94 ++++++++----
>  17 files changed, 475 insertions(+), 178 deletions(-)
> 
> --
> 2.18.2

Series applied to next-net-mlx,

Kindest regards,
Raslan Darawsheh

      parent reply	other threads:[~2023-03-07  9:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-28 16:43 Alexander Kozyrev
2023-02-28 16:43 ` [PATCH 1/5] common/mlx5: detect enhanced CQE compression capability Alexander Kozyrev
2023-03-06 12:33   ` Slava Ovsiienko
2023-02-28 16:43 ` [PATCH 2/5] common/mlx5: add CQE validity iteration count Alexander Kozyrev
2023-03-06 12:39   ` Slava Ovsiienko
2023-02-28 16:43 ` [PATCH 3/5] net/mlx5: support enhanced CQE compression in Rx burst Alexander Kozyrev
2023-03-06 13:01   ` Slava Ovsiienko
2023-02-28 16:43 ` [PATCH 4/5] net/mlx5: support enhanced CQE zipping in vector " Alexander Kozyrev
2023-03-06 13:13   ` Slava Ovsiienko
2023-02-28 16:43 ` [PATCH 5/5] net/mlx5: enable enhanced CQE compression Alexander Kozyrev
2023-03-06 13:14   ` Slava Ovsiienko
2023-03-07  9:03 ` Raslan Darawsheh [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=BYAPR12MB3078E8A16AD6769DDB47B3ACCFB79@BYAPR12MB3078.namprd12.prod.outlook.com \
    --to=rasland@nvidia.com \
    --cc=akozyrev@nvidia.com \
    --cc=dev@dpdk.org \
    --cc=matan@nvidia.com \
    --cc=viacheslavo@nvidia.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).