From: Thomas Monjalon <thomas@monjalon.net>
To: Chaoyong He <chaoyong.he@corigine.com>
Cc: dev@dpdk.org, stable@dpdk.org, oss-drivers@corigine.com,
Shihong Wang <shihong.wang@corigine.com>,
stable@dpdk.org, Akhil Goyal <gakhil@marvell.com>,
Radu Nicolau <radu.nicolau@intel.com>,
Chaoyong He <chaoyong.he@corigine.com>,
Peng Zhang <peng.zhang@corigine.com>
Subject: Re: [PATCH] examples/ipsec-secgw: fix Rx queue ID in Rx callback
Date: Mon, 18 Mar 2024 04:20:15 +0100 [thread overview]
Message-ID: <7014158.18pcnM708K@thomas> (raw)
In-Reply-To: <20240311023247.2520028-1-chaoyong.he@corigine.com>
11/03/2024 03:32, Chaoyong He:
> From: Shihong Wang <shihong.wang@corigine.com>
>
> The Rx queue ID on the core and on the port are not necessarily
> equal, for example, there are two RX queues on core0, queue0 and
> queue1, queue0 is the rx_queueid0 on port0 and queue1 is the
> rx_queueid0 on port1.
>
> The 'rte_eth_add_rx_callback()' function is based on the port
> registration callback function, so should be the RX queue ID on
> the port.
>
> Fixes: d04bb1c52647 ("examples/ipsec-secgw: use HW parsed packet type in poll mode")
> Cc: stable@dpdk.org
> Cc: Akhil Goyal <gakhil@marvell.com>
> Cc: Radu Nicolau <radu.nicolau@intel.com>
>
> Signed-off-by: Shihong Wang <shihong.wang@corigine.com>
> Reviewed-by: Chaoyong He <chaoyong.he@corigine.com>
> Reviewed-by: Peng Zhang <peng.zhang@corigine.com>
Applied, thanks.
prev parent reply other threads:[~2024-03-18 3:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-11 2:32 [PATCH] examples/ipsec-secgw: fix Rx queue ID in Rx callback Chaoyong He
2024-03-18 3:20 ` Thomas Monjalon [this message]
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=7014158.18pcnM708K@thomas \
--to=thomas@monjalon.net \
--cc=chaoyong.he@corigine.com \
--cc=dev@dpdk.org \
--cc=gakhil@marvell.com \
--cc=oss-drivers@corigine.com \
--cc=peng.zhang@corigine.com \
--cc=radu.nicolau@intel.com \
--cc=shihong.wang@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.