From: Steffen Klassert <steffen.klassert@secunet.com>
To: Gauvain Roussel-Tarbouriech <gauvain@govanify.com>
Cc: <netdev@vger.kernel.org>
Subject: Re: UDP GRO without Merging
Date: Wed, 25 Jul 2018 12:52:00 +0200 [thread overview]
Message-ID: <20180725105200.tarhvqw7qac3j2el@gauss3.secunet.de> (raw)
In-Reply-To: <03922960-2b6e-181f-041b-aa636b3c9d98@anarchist.pw>
On Wed, Jul 25, 2018 at 11:53:45AM +0200, Gauvain Roussel-Tarbouriech wrote:
> Subject:
>
> Hello Netdev,
>
> I am working on WireGuard as part of Google Summer of Code and Jason and
> I are working on adding GRO to WireGuard, on the udp_tunnel side of
> things. The goal is to inform udp_tunnel’s gro_receive that certain
> packets are part of the same flow. Then sometime later, we’d like to
> have a list of those same-flow packets appear in gro_complete. As far as
> I can tell, the API seems well suited for merging packets in
> gro_receive, such that gro_complete only then gets one single merged
> packet. However, we need to receive the entire list of same-flow packets
> in gro_complete, unmerged. Is this possible with the present APIs?
We recently posted a patchset that does this GRO packet chaining.
Not sure if this is exactly what you need, but you can have a look here:
https://www.spinics.net/lists/netdev/msg508093.html
This is implemented as a part of a forward fastpath, but
could be also moved generic code if needed.
prev parent reply other threads:[~2018-07-25 12:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-25 9:53 UDP GRO without Merging Gauvain Roussel-Tarbouriech
2018-07-25 10:52 ` 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=20180725105200.tarhvqw7qac3j2el@gauss3.secunet.de \
--to=steffen.klassert@secunet.com \
--cc=gauvain@govanify.com \
--cc=netdev@vger.kernel.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).