From: "Xia, Chenbo" <chenbo.xia@intel.com>
To: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
Boleslav Stankevich <boleslav.stankevich@oktetlabs.ru>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "stable@dpdk.org" <stable@dpdk.org>,
Maxime Coquelin <maxime.coquelin@redhat.com>
Subject: RE: [PATCH v2] net/virtio: deduce IP length for Virtio TSO checksum
Date: Mon, 6 Mar 2023 06:17:20 +0000 [thread overview]
Message-ID: <SN6PR11MB35045F899E3EB542228DFF7E9CB69@SN6PR11MB3504.namprd11.prod.outlook.com> (raw)
In-Reply-To: <af24cd56-4ddb-b580-0696-219f4e1f36f2@oktetlabs.ru>
Hi Boleslav,
The change seems good, but patchwork is complaining about lack of .mailmap change.
http://mails.dpdk.org/archives/test-report/2023-March/363061.html
Guess this is your first patch? So you need to add name and email in mailmap file.
Thanks,
Chenbo
> -----Original Message-----
> From: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
> Sent: Friday, March 3, 2023 11:14 PM
> To: Boleslav Stankevich <boleslav.stankevich@oktetlabs.ru>; dev@dpdk.org
> Cc: stable@dpdk.org; Maxime Coquelin <maxime.coquelin@redhat.com>; Xia,
> Chenbo <chenbo.xia@intel.com>
> Subject: Re: [PATCH v2] net/virtio: deduce IP length for Virtio TSO
> checksum
>
> Cc Maxime and Chenbo
>
> On 3/3/23 14:19, Boleslav Stankevich wrote:
> > The length of TSO payload could not fit into 16 bits provided by the
> > IPv4 total length and IPv6 payload length fields. Thus, deduce it
> > from the length of the packet.
> >
> > Fixes: 696573046e9 ("net/virtio: support TSO")
> > Cc: stable@dpdk.org
> >
> > Signed-off-by: Boleslav Stankevich <boleslav.stankevich@oktetlabs.ru>
> > Reviewed-by: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
> > ---
> > drivers/net/virtio/virtio_rxtx.c | 25 ++++++++++++++++---------
> > 1 file changed, 16 insertions(+), 9 deletions(-)
> >
> > diff --git a/drivers/net/virtio/virtio_rxtx.c
> b/drivers/net/virtio/virtio_rxtx.c
> > index 2d0afd3302..e48ff3cca7 100644
> > --- a/drivers/net/virtio/virtio_rxtx.c
> > +++ b/drivers/net/virtio/virtio_rxtx.c
> > @@ -404,29 +404,36 @@ virtio_tso_fix_cksum(struct rte_mbuf *m)
> > if (likely(rte_pktmbuf_data_len(m) >= m->l2_len + m->l3_len +
> > m->l4_len)) {
> > struct rte_ipv4_hdr *iph;
> > - struct rte_ipv6_hdr *ip6h;
> > struct rte_tcp_hdr *th;
> > - uint16_t prev_cksum, new_cksum, ip_len, ip_paylen;
> > + uint16_t prev_cksum, new_cksum;
> > + uint32_t ip_paylen;
> > uint32_t tmp;
> >
> > iph = rte_pktmbuf_mtod_offset(m,
> > struct rte_ipv4_hdr *, m->l2_len);
> > th = RTE_PTR_ADD(iph, m->l3_len);
> > +
> > + /*
> > + * Calculate IPv4 header checksum with current total length
> value
> > + * (whatever it is) to have correct checksum after update on
> edits
> > + * done by TSO.
> > + */
> > if ((iph->version_ihl >> 4) == 4) {
> > iph->hdr_checksum = 0;
> > iph->hdr_checksum = rte_ipv4_cksum(iph);
> > - ip_len = iph->total_length;
> > - ip_paylen = rte_cpu_to_be_16(rte_be_to_cpu_16(ip_len) -
> > - m->l3_len);
> > - } else {
> > - ip6h = (struct rte_ipv6_hdr *)iph;
> > - ip_paylen = ip6h->payload_len;
> > }
> >
> > + /*
> > + * Do not use IPv4 total length and IPv6 payload length fields
> to get
> > + * TSO payload length since it could not fit into 16 bits.
> > + */
> > + ip_paylen = rte_cpu_to_be_32(rte_pktmbuf_pkt_len(m) - m-
> >l2_len -
> > + m->l3_len);
> > +
> > /* calculate the new phdr checksum not including ip_paylen */
> > prev_cksum = th->cksum;
> > tmp = prev_cksum;
> > - tmp += ip_paylen;
> > + tmp += (ip_paylen & 0xffff) + (ip_paylen >> 16);
> > tmp = (tmp & 0xffff) + (tmp >> 16);
> > new_cksum = tmp;
> >
next prev parent reply other threads:[~2023-03-06 6:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230216123554.2628837-2-boleslav.stankevich@oktetlabs.ru>
2023-03-03 11:19 ` Boleslav Stankevich
2023-03-03 15:13 ` Andrew Rybchenko
2023-03-06 6:17 ` Xia, Chenbo [this message]
2023-03-06 10:57 ` Maxime Coquelin
2023-03-06 14:13 ` Maxime Coquelin
2023-03-06 14:20 ` Maxime Coquelin
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=SN6PR11MB35045F899E3EB542228DFF7E9CB69@SN6PR11MB3504.namprd11.prod.outlook.com \
--to=chenbo.xia@intel.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=boleslav.stankevich@oktetlabs.ru \
--cc=dev@dpdk.org \
--cc=maxime.coquelin@redhat.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).