patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Andrew Rybchenko <arybchenko@solarflare.com>
To: <stable@dpdk.org>
Subject: [dpdk-stable] [PATCH 17.11] net/sfc: pass HW Tx queue index on creation
Date: Mon, 11 Mar 2019 08:44:14 +0000	[thread overview]
Message-ID: <1552293856-24222-1-git-send-email-arybchenko@solarflare.com> (raw)

[ backported from upstream commit 7928b0fdf8f790b6178ad91cf41ee2f9df10e707 ]

Software indexes are PMD internal and should not be passed outside.
Right now SW and HW indexes of the Tx queue match, so it is just
a cosmetic fix.

Fixes: dbdc82416b72 ("net/sfc: factor out libefx-based Tx datapath")

Signed-off-by: Andrew Rybchenko <arybchenko@solarflare.com>
---
 drivers/net/sfc/sfc_tx.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/net/sfc/sfc_tx.c b/drivers/net/sfc/sfc_tx.c
index 9b1e654..72245cf 100644
--- a/drivers/net/sfc/sfc_tx.c
+++ b/drivers/net/sfc/sfc_tx.c
@@ -449,7 +449,7 @@
 			flags |= EFX_TXQ_FATSOV2;
 	}
 
-	rc = efx_tx_qcreate(sa->nic, sw_index, 0, &txq->mem,
+	rc = efx_tx_qcreate(sa->nic, txq->hw_index, 0, &txq->mem,
 			    txq_info->entries, 0 /* not used on EF10 */,
 			    flags, evq->common,
 			    &txq->common, &desc_index);
-- 
1.8.3.1

             reply	other threads:[~2019-03-11  8:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-11  8:44 Andrew Rybchenko [this message]
2019-03-11  8:44 ` [dpdk-stable] [PATCH 17.11] net/sfc/base: fix Tx descriptor max number check Andrew Rybchenko
2019-03-12 22:15   ` Yongseok Koh
2019-03-11  8:44 ` [dpdk-stable] [PATCH 17.11] net/sfc: fix port ID log Andrew Rybchenko
2019-03-12 22:15   ` Yongseok Koh
2019-03-12 22:15 ` [dpdk-stable] [PATCH 17.11] net/sfc: pass HW Tx queue index on creation Yongseok Koh

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=1552293856-24222-1-git-send-email-arybchenko@solarflare.com \
    --to=arybchenko@solarflare.com \
    --cc=stable@dpdk.org \
    /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).