DPDK patches and discussions
 help / color / mirror / Atom feed
From: Alexander Kozyrev <akozyrev@nvidia.com>
To: dev@dpdk.org
Cc: rasland@nvidia.com, matan@nvidia.com, viacheslavo@nvidia.com
Subject: [dpdk-dev] [PATCH 0/4] net/mlx5: use C11 atomic builtins
Date: Tue, 27 Oct 2020 15:28:20 +0000	[thread overview]
Message-ID: <20201027152824.15232-1-akozyrev@nvidia.com> (raw)

The rte_atomic API is deprecated and needs to be
replaced with C11 atomic builtins in MLX5 driver.

Alexander Kozyrev (4):
  common/mlx5: use C11 atomics for memory allocation
  common/mlx5: use C11 atomics for netlink sequence
  net/mlx5: use C11 atomics for RxQ/TxQ refcounts
  net/mlx5: use C11 atomics for RTE flow tables

 drivers/common/mlx5/linux/mlx5_nl.c     |   5 +-
 drivers/common/mlx5/mlx5_malloc.c       |  91 ++++++++---------
 drivers/net/mlx5/linux/mlx5_ethdev_os.c |   1 -
 drivers/net/mlx5/mlx5.c                 |   9 +-
 drivers/net/mlx5/mlx5.h                 |  15 ++-
 drivers/net/mlx5/mlx5_ethdev.c          |   1 -
 drivers/net/mlx5/mlx5_flow.h            |  15 ++-
 drivers/net/mlx5/mlx5_flow_dv.c         | 126 +++++++++++++-----------
 drivers/net/mlx5/mlx5_rxq.c             |  28 +++---
 drivers/net/mlx5/mlx5_txq.c             |   8 +-
 10 files changed, 153 insertions(+), 146 deletions(-)

-- 
2.24.1


             reply	other threads:[~2020-10-27 15:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-27 15:28 Alexander Kozyrev [this message]
2020-10-27 15:28 ` [dpdk-dev] [PATCH 1/4] common/mlx5: use C11 atomics for memory allocation Alexander Kozyrev
2020-10-27 15:28 ` [dpdk-dev] [PATCH 2/4] common/mlx5: use C11 atomics for netlink sequence Alexander Kozyrev
2020-10-27 15:28 ` [dpdk-dev] [PATCH 3/4] net/mlx5: use C11 atomics for RxQ/TxQ refcounts Alexander Kozyrev
2020-10-27 15:28 ` [dpdk-dev] [PATCH 4/4] net/mlx5: use C11 atomics for RTE flow tables Alexander Kozyrev
2020-10-27 22:29 ` [dpdk-dev] [PATCH 0/4] net/mlx5: use C11 atomic builtins Raslan Darawsheh

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=20201027152824.15232-1-akozyrev@nvidia.com \
    --to=akozyrev@nvidia.com \
    --cc=dev@dpdk.org \
    --cc=matan@nvidia.com \
    --cc=rasland@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).