DPDK patches and discussions
 help / color / mirror / Atom feed
From: Li RongQing <lirongqing@baidu.com>
To: dev@dpdk.org
Subject: [dpdk-dev] [PATCH 2/2] net/bonding: fix RX queue conversion
Date: Tue, 22 Sep 2020 18:29:32 +0800	[thread overview]
Message-ID: <1600770572-22716-2-git-send-email-lirongqing@baidu.com> (raw)
In-Reply-To: <1600770572-22716-1-git-send-email-lirongqing@baidu.com>

From: Dongsheng Rong <rongdongsheng@baidu.com>

it should be bond_rx_queue in bond_ethdev_rx_burst_alb in
RX path, not bond_tx_queue

Fixes: 06fe78b98ccd ("bond: add mode 6")

Signed-off-by: Dongsheng Rong <rongdongsheng@baidu.com>
Signed-off-by: Li RongQing <lirongqing@baidu.com>
---
 drivers/net/bonding/rte_eth_bond_pmd.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/drivers/net/bonding/rte_eth_bond_pmd.c b/drivers/net/bonding/rte_eth_bond_pmd.c
index 146d4dc4a..01ae8e902 100644
--- a/drivers/net/bonding/rte_eth_bond_pmd.c
+++ b/drivers/net/bonding/rte_eth_bond_pmd.c
@@ -534,8 +534,8 @@ mode6_debug(const char __rte_unused *info,
 static uint16_t
 bond_ethdev_rx_burst_alb(void *queue, struct rte_mbuf **bufs, uint16_t nb_pkts)
 {
-	struct bond_tx_queue *bd_tx_q = (struct bond_tx_queue *)queue;
-	struct bond_dev_private *internals = bd_tx_q->dev_private;
+	struct bond_rx_queue *bd_rx_q = (struct bond_rx_queue *)queue;
+	struct bond_dev_private *internals = bd_rx_q->dev_private;
 	struct rte_ether_hdr *eth_h;
 	uint16_t ether_type, offset;
 	uint16_t nb_recv_pkts;
-- 
2.16.2


  reply	other threads:[~2020-09-22 10:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-22 10:29 [dpdk-dev] [PATCH 1/2] net/bonding: fix a possible unbalance packet receiving Li RongQing
2020-09-22 10:29 ` Li RongQing [this message]
2020-09-30  5:40 ` [dpdk-dev] [PATCH] " Li RongQing
2020-09-30  8:40   ` Wei Hu (Xavier)
2020-09-30  9:12     ` Li,Rongqing
2020-10-09 11:56     ` Li,Rongqing
2020-10-09 12:04       ` Ferruh Yigit
2020-10-09 13:44 ` [dpdk-dev] [PATCH 1/2] " 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=1600770572-22716-2-git-send-email-lirongqing@baidu.com \
    --to=lirongqing@baidu.com \
    --cc=dev@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).