From: Xueming Li <xuemingl@nvidia.com>
To: Chaoyong He <chaoyong.he@corigine.com>,
"stable@dpdk.org" <stable@dpdk.org>
Cc: "oss-drivers@corigine.com" <oss-drivers@corigine.com>,
Long Wu <long.wu@corigine.com>,
Peng Zhang <peng.zhang@corigine.com>
Subject: Re: [PATCH 23.11] net/nfp: fix port ID meta data use in Rx
Date: Wed, 1 May 2024 01:19:25 +0000 [thread overview]
Message-ID: <DM4PR12MB537395786162D749420341D0A1192@DM4PR12MB5373.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20240415024008.1000358-1-chaoyong.he@corigine.com>
[-- Attachment #1: Type: text/plain, Size: 1654 bytes --]
Hi Chaoyong,
Thanks for your help, patch added into release queue.
________________________________
From: Chaoyong He <chaoyong.he@corigine.com>
Sent: Monday, April 15, 2024 10:40 AM
To: stable@dpdk.org <stable@dpdk.org>
Cc: oss-drivers@corigine.com <oss-drivers@corigine.com>; Long Wu <long.wu@corigine.com>; Chaoyong He <chaoyong.he@corigine.com>; Peng Zhang <peng.zhang@corigine.com>
Subject: [PATCH 23.11] net/nfp: fix port ID meta data use in Rx
From: Long Wu <long.wu@corigine.com>
[ upstream commit ddc84b53f38281ff2c15f7feb7e3a0b556dd92b2 ]
Meta data parsing should be controlled by meta data flag. So use
flag to determine if receive function can use 'port_id' meta data.
Fixes: 580ea0b09a7c ("net/nfp: fix Rx descriptor")
Signed-off-by: Long Wu <long.wu@corigine.com>
Reviewed-by: Chaoyong He <chaoyong.he@corigine.com>
Reviewed-by: Peng Zhang <peng.zhang@corigine.com>
---
drivers/net/nfp/nfp_rxtx.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net/nfp/nfp_rxtx.c b/drivers/net/nfp/nfp_rxtx.c
index 8ca651ba55..5033d659d3 100644
--- a/drivers/net/nfp/nfp_rxtx.c
+++ b/drivers/net/nfp/nfp_rxtx.c
@@ -760,7 +760,7 @@ nfp_net_recv_pkts(void *rx_queue,
if (unlikely(rxq->rd_p == rxq->rx_count)) /* Wrapping */
rxq->rd_p = 0;
- if (meta.port_id == 0) {
+ if (((meta.flags >> NFP_NET_META_PORTID) & 0x1) == 0) {
rx_pkts[avail++] = mb;
} else if (nfp_flower_pf_dispatch_pkts(hw, mb, meta.port_id)) {
avail_multiplexed++;
--
2.27.0
[-- Attachment #2: Type: text/html, Size: 3673 bytes --]
next prev parent reply other threads:[~2024-05-01 1:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-15 2:40 Chaoyong He
2024-05-01 1:19 ` Xueming Li [this message]
2024-05-01 1:50 ` Xueming Li
2024-05-07 1:56 ` Chaoyong He
2024-05-07 2:05 ` Xueming Li
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=DM4PR12MB537395786162D749420341D0A1192@DM4PR12MB5373.namprd12.prod.outlook.com \
--to=xuemingl@nvidia.com \
--cc=chaoyong.he@corigine.com \
--cc=long.wu@corigine.com \
--cc=oss-drivers@corigine.com \
--cc=peng.zhang@corigine.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).