From: "Li, HongboX" <hongbox.li@intel.com>
To: "Ye, MingjinX" <mingjinx.ye@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "Ye, MingjinX" <mingjinx.ye@intel.com>,
"stable@dpdk.org" <stable@dpdk.org>
Subject: RE: [PATCH 2/2] net/ice: Tx path check mbuf sub-segment
Date: Thu, 21 Mar 2024 02:10:19 +0000 [thread overview]
Message-ID: <PH8PR11MB7120A72253D657406CD8AC529F322@PH8PR11MB7120.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20240315102409.1079521-3-mingjinx.ye@intel.com>
> -----Original Message-----
> From: Mingjin Ye <mingjinx.ye@intel.com>
> Sent: Friday, March 15, 2024 6:24 PM
> To: dev@dpdk.org
> Cc: Ye, MingjinX <mingjinx.ye@intel.com>; stable@dpdk.org
> Subject: [PATCH 2/2] net/ice: Tx path check mbuf sub-segment
>
> Add check mbuf sub-segment to Tx diagnostic path.
>
> Fixes: 2a0244d611b4 ("net/ice: support mbuf checks in Tx path")
> Cc: stable@dpdk.org
>
> Signed-off-by: Mingjin Ye <mingjinx.ye@intel.com>
> ---
> drivers/net/ice/ice_rxtx.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/net/ice/ice_rxtx.c b/drivers/net/ice/ice_rxtx.c index
> 13aabe97a5..31a3a35c1d 100644
> --- a/drivers/net/ice/ice_rxtx.c
> +++ b/drivers/net/ice/ice_rxtx.c
> @@ -3713,7 +3713,7 @@ ice_xmit_pkts_check(void *tx_queue, struct
> rte_mbuf **tx_pkts, uint16_t nb_pkts)
> ol_flags = mb->ol_flags;
>
> if ((adapter->devargs.mbuf_check &
> ICE_MBUF_CHECK_F_TX_MBUF) &&
> - (rte_mbuf_check(mb, 0, &reason) != 0)) {
> + (rte_mbuf_check(mb, 1, &reason) != 0)) {
> PMD_TX_LOG(ERR, "INVALID mbuf: %s\n", reason);
> pkt_error = true;
> break;
> --
> 2.25.1
Tested-by: Li, HongboX <hongbox.li@intel.com>
next prev parent reply other threads:[~2024-03-21 2:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240315102409.1079521-1-mingjinx.ye@intel.com>
2024-03-15 10:24 ` [PATCH 1/2] net/i40e: " Mingjin Ye
2024-03-15 10:24 ` [PATCH 2/2] net/ice: " Mingjin Ye
2024-03-21 2:10 ` Li, HongboX [this message]
2024-03-19 9:39 ` [PATCH 0/2] " Li, HongboX
2024-04-04 10:12 ` Bruce Richardson
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=PH8PR11MB7120A72253D657406CD8AC529F322@PH8PR11MB7120.namprd11.prod.outlook.com \
--to=hongbox.li@intel.com \
--cc=dev@dpdk.org \
--cc=mingjinx.ye@intel.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).