From: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
To: <dev@dpdk.org>
Cc: <rasland@nvidia.com>, <matan@nvidia.com>, <suanmingm@nvidia.com>,
<dsosnowski@nvidia.com>
Subject: [PATCH] net/mlx5: cleanup unused Tx doorbelling routine
Date: Mon, 23 Mar 2026 12:14:10 +0200 [thread overview]
Message-ID: <20260323101410.393887-1-viacheslavo@nvidia.com> (raw)
The mlx5_tx_dbrec() was replaced with common mlx5_doorbell_ring()
routine and is not needed anymore.
Signed-off-by: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
Acked-by: Dariusz Sosnowski <dsosnowski@nvidia.com>
---
drivers/net/mlx5/mlx5_tx.h | 15 ---------------
1 file changed, 15 deletions(-)
diff --git a/drivers/net/mlx5/mlx5_tx.h b/drivers/net/mlx5/mlx5_tx.h
index 48dbb2d867..016dba0b03 100644
--- a/drivers/net/mlx5/mlx5_tx.h
+++ b/drivers/net/mlx5/mlx5_tx.h
@@ -301,21 +301,6 @@ mlx5_tx_bfreg(struct mlx5_txq_data *txq)
return &MLX5_PROC_PRIV(txq->port_id)->uar_table[txq->idx];
}
-/**
- * Ring TX queue doorbell and flush the update by write memory barrier.
- *
- * @param txq
- * Pointer to TX queue structure.
- * @param wqe
- * Pointer to the last WQE posted in the NIC.
- */
-static __rte_always_inline void
-mlx5_tx_dbrec(struct mlx5_txq_data *txq, volatile struct mlx5_wqe *wqe)
-{
- mlx5_doorbell_ring(mlx5_tx_bfreg(txq), *(volatile uint64_t *)wqe,
- txq->wqe_ci, txq->qp_db, 1);
-}
-
/**
* Convert timestamp from mbuf format to linear counter
* of Clock Queue completions (24 bits).
--
2.34.1
next reply other threads:[~2026-03-23 10:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-23 10:14 Viacheslav Ovsiienko [this message]
2026-03-24 12:57 ` [PATCH] net/mlx5: cleanup unused Tx doorbelling routine 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=20260323101410.393887-1-viacheslavo@nvidia.com \
--to=viacheslavo@nvidia.com \
--cc=dev@dpdk.org \
--cc=dsosnowski@nvidia.com \
--cc=matan@nvidia.com \
--cc=rasland@nvidia.com \
--cc=suanmingm@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