netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
To: Steffen Klassert <steffen.klassert@secunet.com>
Cc: David Miller <davem@davemloft.net>,
	Paolo Abeni <pabeni@redhat.com>,
	Subash Abhinov Kasiviswanathan <subashab@codeaurora.org>,
	Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>,
	Network Development <netdev@vger.kernel.org>
Subject: Re: [PATCH net-next v3 4/4] udp: Support UDP fraglist GRO/GSO.
Date: Sat, 25 Jan 2020 10:31:30 -0500	[thread overview]
Message-ID: <CA+FuTSdQWBbyMyPd27oMHG8sL5F+A6tqReN30JiNNQMYXjeSnw@mail.gmail.com> (raw)
In-Reply-To: <20200125102645.4782-5-steffen.klassert@secunet.com>

On Sat, Jan 25, 2020 at 5:26 AM Steffen Klassert
<steffen.klassert@secunet.com> wrote:
>
> This patch extends UDP GRO to support fraglist GRO/GSO
> by using the previously introduced infrastructure.
> If the feature is enabled, all UDP packets are going to
> fraglist GRO (local input and forward).
>
> After validating the csum,  we mark ip_summed as
> CHECKSUM_UNNECESSARY for fraglist GRO packets to
> make sure that the csum is not touched.
>
> Signed-off-by: Steffen Klassert <steffen.klassert@secunet.com>

Reviewed-by: Willem de Bruijn <willemb@google.com>

  reply	other threads:[~2020-01-25 15:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-25 10:26 [PATCH net-next v3 0/4] Support fraglist GRO/GSO Steffen Klassert
2020-01-25 10:26 ` [PATCH net-next v3 1/4] net: Add fraglist GRO/GSO feature flags Steffen Klassert
2020-01-25 10:26 ` [PATCH net-next v3 2/4] net: Add a netdev software feature set that defaults to off Steffen Klassert
2020-01-25 10:26 ` [PATCH net-next v3 3/4] net: Support GRO/GSO fraglist chaining Steffen Klassert
2020-01-25 10:26 ` [PATCH net-next v3 4/4] udp: Support UDP fraglist GRO/GSO Steffen Klassert
2020-01-25 15:31   ` Willem de Bruijn [this message]
2020-01-27 10:00 ` [PATCH net-next v3 0/4] Support " David Miller

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=CA+FuTSdQWBbyMyPd27oMHG8sL5F+A6tqReN30JiNNQMYXjeSnw@mail.gmail.com \
    --to=willemdebruijn.kernel@gmail.com \
    --cc=davem@davemloft.net \
    --cc=marcelo.leitner@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=steffen.klassert@secunet.com \
    --cc=subashab@codeaurora.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).