From: Christian Ehrhardt <christian.ehrhardt@canonical.com>
To: Wenwu Ma <wenwux.ma@intel.com>
Cc: stable@dpdk.org, Jiayu Hu <jiayu.hu@intel.com>,
Wei Ling <weix.ling@intel.com>,
Yuying Zhang <yuying.zhang@intel.com>
Subject: Re: [PATCH 19.11] app/testpmd: perform SW IP checksum for GRO/GSO packets
Date: Fri, 8 Jul 2022 10:08:08 +0200 [thread overview]
Message-ID: <CAATJJ0KZzweJKRnSmwGzR3PbNMUOxAS85QUR4CoNLpxLZDZdRg@mail.gmail.com> (raw)
In-Reply-To: <20220708025343.344065-1-wenwux.ma@intel.com>
On Fri, Jul 8, 2022 at 4:58 AM Wenwu Ma <wenwux.ma@intel.com> wrote:
>
> upstream commit 1945c64674b2b9ad55af0ef31f8a02ae0b747400
Thank you, applied to the WIP branch for 19.11.13
> The GRO/GSO library doesn't re-calculate checksums for
> merged/fragmented packets. If users want the packets to
> have correct IP checksums, they should select HW IP
> checksum calculation for the port which the packets are
> transmitted to. But if the port doesn't support HW IP
> checksum, users may perform a SW IP checksum.
>
> Fixes: b7091f1dcfbc ("app/testpmd: enable the heavyweight mode TCP/IPv4 GRO")
> Fixes: 52f38a2055ed ("app/testpmd: enable TCP/IPv4 VxLAN and GRE GSO")
>
> Signed-off-by: Wenwu Ma <wenwux.ma@intel.com>
> Reviewed-by: Jiayu Hu <jiayu.hu@intel.com>
> Tested-by: Wei Ling <weix.ling@intel.com>
> Acked-by: Yuying Zhang <yuying.zhang@intel.com>
> ---
> app/test-pmd/csumonly.c | 24 ++++++++++++++++++++++++
> 1 file changed, 24 insertions(+)
>
> diff --git a/app/test-pmd/csumonly.c b/app/test-pmd/csumonly.c
> index 25091de881..117f14451d 100644
> --- a/app/test-pmd/csumonly.c
> +++ b/app/test-pmd/csumonly.c
> @@ -731,6 +731,26 @@ pkt_copy_split(const struct rte_mbuf *pkt)
> return md[0];
> }
>
> +/*
> + * Re-calculate IP checksum for merged/fragmented packets.
> + */
> +static void
> +pkts_ip_csum_recalc(struct rte_mbuf **pkts_burst, const uint16_t nb_pkts, uint64_t tx_offloads)
> +{
> + int i;
> + struct rte_ipv4_hdr *ipv4_hdr;
> + for (i = 0; i < nb_pkts; i++) {
> + if ((pkts_burst[i]->ol_flags & PKT_TX_IPV4) &&
> + (tx_offloads & DEV_TX_OFFLOAD_IPV4_CKSUM) == 0) {
> + ipv4_hdr = rte_pktmbuf_mtod_offset(pkts_burst[i],
> + struct rte_ipv4_hdr *,
> + pkts_burst[i]->l2_len);
> + ipv4_hdr->hdr_checksum = 0;
> + ipv4_hdr->hdr_checksum = rte_ipv4_cksum(ipv4_hdr);
> + }
> + }
> +}
> +
> /*
> * Receive a burst of packets, and for each packet:
> * - parse packet, and try to recognize a supported packet type (1)
> @@ -1038,6 +1058,8 @@ pkt_burst_checksum_forward(struct fwd_stream *fs)
> fs->gro_times = 0;
> }
> }
> +
> + pkts_ip_csum_recalc(pkts_burst, nb_rx, tx_offloads);
> }
>
> if (gso_ports[fs->tx_port].enable == 0)
> @@ -1059,6 +1081,8 @@ pkt_burst_checksum_forward(struct fwd_stream *fs)
>
> tx_pkts_burst = gso_segments;
> nb_rx = nb_segments;
> +
> + pkts_ip_csum_recalc(tx_pkts_burst, nb_rx, tx_offloads);
> }
>
> nb_prep = rte_eth_tx_prepare(fs->tx_port, fs->tx_queue,
> --
> 2.25.1
>
--
Christian Ehrhardt
Senior Staff Engineer, Ubuntu Server
Canonical Ltd
prev parent reply other threads:[~2022-07-08 8:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-08 2:53 Wenwu Ma
2022-07-08 8:08 ` Christian Ehrhardt [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=CAATJJ0KZzweJKRnSmwGzR3PbNMUOxAS85QUR4CoNLpxLZDZdRg@mail.gmail.com \
--to=christian.ehrhardt@canonical.com \
--cc=jiayu.hu@intel.com \
--cc=stable@dpdk.org \
--cc=weix.ling@intel.com \
--cc=wenwux.ma@intel.com \
--cc=yuying.zhang@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).