From: Steffen Klassert <steffen.klassert@secunet.com>
To: Dongseok Yi <dseok.yi@samsung.com>
Cc: "'David S. Miller'" <davem@davemloft.net>,
'Alexander Lobakin' <alobakin@pm.me>, <namkyu78.kim@samsung.com>,
'Jakub Kicinski' <kuba@kernel.org>,
'Hideaki YOSHIFUJI' <yoshfuji@linux-ipv6.org>,
"'Willem de Bruijn'" <willemb@google.com>,
<netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net v3] udp: ipv4: manipulate network header of NATed UDP GRO fraglist
Date: Tue, 26 Jan 2021 13:50:27 +0100 [thread overview]
Message-ID: <20210126125027.GX3576117@gauss3.secunet.de> (raw)
In-Reply-To: <026001d6f37a$97461300$c5d23900$@samsung.com>
On Tue, Jan 26, 2021 at 09:31:29AM +0900, Dongseok Yi wrote:
> On 1/25/21 9:45 PM, Steffen Klassert wrote:
> > On Thu, Jan 21, 2021 at 10:24:39PM +0900, Dongseok Yi wrote:
> > >
> > > +static void __udpv4_gso_segment_csum(struct sk_buff *seg,
> > > + __be32 *oldip, __be32 *newip,
> > > + __be16 *oldport, __be16 *newport)
> > > +{
> > > + struct udphdr *uh;
> > > + struct iphdr *iph;
> > > +
> > > + if (*oldip == *newip && *oldport == *newport)
> > > + return;
> >
> > This check is redundant as you check this already in
> > __udpv4_gso_segment_list_csum.
>
> When comes in __udpv4_gso_segment_csum, the condition would be
> SNAT or DNAT. I think we don't need to do the function if the
> condition is not met. I want to skip the function for SNAT checksum
> when DNAT only case. Is it better to remove the check?
Ok, so it can be seen as an optimization. It is ok as it is.
Acked-by: Steffen Klassert <steffen.klassert@secunet.com>
Thanks!
prev parent reply other threads:[~2021-01-26 12:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20210121133649epcas2p493d5d59df1b48ee8e3282ab766f37a70@epcas2p4.samsung.com>
2021-01-21 13:24 ` Dongseok Yi
2021-01-25 12:45 ` Steffen Klassert
2021-01-26 0:31 ` Dongseok Yi
2021-01-26 12:50 ` Steffen Klassert [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=20210126125027.GX3576117@gauss3.secunet.de \
--to=steffen.klassert@secunet.com \
--cc=alobakin@pm.me \
--cc=davem@davemloft.net \
--cc=dseok.yi@samsung.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=namkyu78.kim@samsung.com \
--cc=netdev@vger.kernel.org \
--cc=willemb@google.com \
--cc=yoshfuji@linux-ipv6.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
all inboxes | Powered by JetHome®