From: Jerin Jacob <jerinj@marvell.com>
To: Rahul Bhansali <rbhansali@marvell.com>,
"dev@dpdk.org" <dev@dpdk.org>,
Nithin Kumar Dabilpuram <ndabilpuram@marvell.com>,
Kiran Kumar Kokkilagadda <kirankumark@marvell.com>,
Sunil Kumar Kori <skori@marvell.com>,
Satha Koteswara Rao Kottidi <skoteshwar@marvell.com>,
Harman Kalra <hkalra@marvell.com>,
Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>,
Rahul Bhansali <rbhansali@marvell.com>
Subject: RE: [PATCH v2] net/cnxk: fix of NIX send header L3 type
Date: Tue, 4 Feb 2025 17:00:04 +0000 [thread overview]
Message-ID: <BY3PR18MB4785CCF9298A723023F358C3C8F42@BY3PR18MB4785.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20250130115526.1023855-1-rbhansali@marvell.com>
> -----Original Message-----
> From: Rahul Bhansali <rbhansali@marvell.com>
> Sent: Thursday, January 30, 2025 5:25 PM
> To: dev@dpdk.org; Nithin Kumar Dabilpuram <ndabilpuram@marvell.com>;
> Kiran Kumar Kokkilagadda <kirankumark@marvell.com>; Sunil Kumar Kori
> <skori@marvell.com>; Satha Koteswara Rao Kottidi
> <skoteshwar@marvell.com>; Harman Kalra <hkalra@marvell.com>; Pavan
> Nikhilesh Bhagavatula <pbhagavatula@marvell.com>; Jerin Jacob
> <jerinj@marvell.com>; Rahul Bhansali <rbhansali@marvell.com>
> Subject: [PATCH v2] net/cnxk: fix of NIX send header L3 type
>
> For small packets less than 55 bytes, SQ error interrupts are observed.
> When checksum offload flag is enabled and mbuf ol_flags are not set, then
> default L3 type will be set to IPv6 in vector processing. Based on this, HW will
> still validate for minimum header size and generate send header error if
> mismatch.
>
> To address this, will set default L3 type to none. Mbuf ol_flags
> RTE_MBUF_F_TX_IPV6 will set with offload feature TSO or L4 checksum only, so
> handled in corresponding routine.
>
> Fixes: f71b7dbbf04b ("net/cnxk: add vector Tx for CN10K")
> Fixes: e829e60c6917 ("net/cnxk: support Tx burst vector for CN20K")
> Fixes: 862e28128707 ("net/cnxk: add vector Tx for CN9K")
>
> Signed-off-by: Rahul Bhansali <rbhansali@marvell.com>
Applied to dpdk-next-net-mrvl/for-main. Thanks
prev parent reply other threads:[~2025-02-04 17:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-27 6:33 [PATCH] " Rahul Bhansali
2025-01-30 11:55 ` [PATCH v2] " Rahul Bhansali
2025-02-04 17:00 ` Jerin Jacob [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=BY3PR18MB4785CCF9298A723023F358C3C8F42@BY3PR18MB4785.namprd18.prod.outlook.com \
--to=jerinj@marvell.com \
--cc=dev@dpdk.org \
--cc=hkalra@marvell.com \
--cc=kirankumark@marvell.com \
--cc=ndabilpuram@marvell.com \
--cc=pbhagavatula@marvell.com \
--cc=rbhansali@marvell.com \
--cc=skori@marvell.com \
--cc=skoteshwar@marvell.com \
/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).