From: Thomas Monjalon <thomas@monjalon.net>
To: Mohsin Kazmi <mohsin.kazmi14@gmail.com>
Cc: Olivier Matz <olivier.matz@6wind.com>,
dev@dpdk.org, ray.kinsella@intel.com, stable@dpdk.org,
Tomasz Kulasek <tomaszx.kulasek@intel.com>,
Konstantin Ananyev <konstantin.ananyev@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2] net: prepare the outer ipv4 hdr for checksum
Date: Thu, 22 Jul 2021 21:53:31 +0200 [thread overview]
Message-ID: <4459484.c67x3OAJy8@thomas> (raw)
In-Reply-To: <CAKkt9++9mJoUOsmVTfZwP-fS651RMyHvDdCHSJgE8om0pB+wzw@mail.gmail.com>
07/07/2021 11:14, Mohsin Kazmi:
> On Wed, Jun 30, 2021 at 3:09 PM Olivier Matz <olivier.matz@6wind.com> wrote:
> > > + if (ol_flags & (PKT_TX_OUTER_IPV4 | PKT_TX_OUTER_IPV6)) {
> > > inner_l3_offset += m->outer_l2_len + m->outer_l3_len;
> > > + /*
> > > + * prepare outer ipv4 header checksum by setting it to 0,
> > > + * in order to be computed by hardware NICs.
> > > + */
> > > + if (ol_flags & PKT_TX_OUTER_IP_CKSUM) {
> > > + ipv4_hdr = rte_pktmbuf_mtod_offset(m,
> > > + struct rte_ipv4_hdr *,
> > m->outer_l2_len);
> > > + ipv4_hdr->hdr_checksum = 0;
> > > + }
> > > + }
> >
> > What about outer L4 checksum? Does it requires the same than inner?
> >
> I am using XL710 for my testing with i40e dpdk driver. AFAIK, It doesn't
> support outer l4 checksum. I am not sure if other Intel NICs support it.
This function is used by a lot of drivers.
Try git grep rte_net_intel_cksum_prepare
I think we need more reviews on the v3.
Given it is far from being a new bug, I suggest to wait the next release
in order to have more feedbacks.
next prev parent reply other threads:[~2021-07-22 19:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-30 11:04 Mohsin Kazmi
2021-06-30 14:09 ` Olivier Matz
2021-07-07 9:14 ` Mohsin Kazmi
2021-07-22 19:53 ` Thomas Monjalon [this message]
2021-08-03 12:29 ` Mohsin Kazmi
2021-07-07 9:40 ` [dpdk-dev] [PATCH v3] net: fix Intel-specific Prepare " Mohsin Kazmi
2021-07-22 19:56 ` [dpdk-dev] [dpdk-stable] " Thomas Monjalon
2021-07-27 12:52 ` Olivier Matz
2021-07-28 15:46 ` [dpdk-dev] " Andrew Rybchenko
2021-07-30 11:11 ` Olivier Matz
2021-07-31 12:49 ` Andrew Rybchenko
2021-08-03 12:49 ` Mohsin Kazmi
2021-08-27 13:44 ` Mohsin Kazmi
2021-09-07 10:49 ` [dpdk-dev] [PATCH v4] net: fix Intel-specific Prepare the outer IPv4 " Mohsin Kazmi
2021-09-15 10:39 ` Ferruh Yigit
2021-09-15 11:04 ` 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=4459484.c67x3OAJy8@thomas \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=konstantin.ananyev@intel.com \
--cc=mohsin.kazmi14@gmail.com \
--cc=olivier.matz@6wind.com \
--cc=ray.kinsella@intel.com \
--cc=stable@dpdk.org \
--cc=tomaszx.kulasek@intel.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).