From: "Marek Behún" <kabel@kernel.org>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Sven Auhagen <sven.auhagen@voleatech.de>,
netdev@vger.kernel.org, davem@davemloft.net,
Jakub Kicinski <kuba@kernel.org>,
Matteo Croce <mcroce@microsoft.com>,
Lorenzo Bianconi <lorenzo@kernel.org>
Subject: Re: [PATCH net-next] net: mvpp2: increase MTU limit when XDP enabled
Date: Wed, 6 Jan 2021 13:32:05 +0100 [thread overview]
Message-ID: <20210106133205.617dddd8@kernel.org> (raw)
In-Reply-To: <20210106125608.5f6fab6f@kernel.org>
On Wed, 6 Jan 2021 12:56:08 +0100
Marek Behún <kabel@kernel.org> wrote:
> I also to write a simple NAT masquerading program. I think XDP can
> increase NAT throughput to 2.5gbps as well.
BTW currently if XDP modifies the packet, it has to modify the
checksums accordingly. There is a helper for that even, bpf_csum_diff.
But many drivers can offload csum computation, mvneta and mvpp2 for
example. But for this, somehow the XDP program has to let the driver
know what kind of csum it needs to be computed (L3, L4 TCP/UDP).
This could theoretically be communicated with the driver via metadata
prepended to the packet. But a abstraction is needed, so that every
driver does it in the same way. Maybe someone is already working on
this, I don't know...
Marek
next prev parent reply other threads:[~2021-01-06 12:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-05 17:19 [PATCH net-next] net: mvpp2: increase MTU limit when XDP enabled Marek Behún
2021-01-05 17:24 ` Sven Auhagen
2021-01-05 17:43 ` Marek Behún
2021-01-05 20:21 ` Andrew Lunn
2021-01-06 11:56 ` Marek Behún
2021-01-06 12:32 ` Marek Behún [this message]
2021-01-06 12:33 ` Marek Behún
2021-01-06 18:34 ` Andrew Lunn
2021-01-06 13:13 ` Vladimir Oltean
2021-01-06 10:33 ` Jesper Dangaard Brouer
2021-01-06 11:28 ` Sven Auhagen
2021-01-05 20:23 ` Andrew Lunn
2021-01-06 12:11 ` Marek Behún
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=20210106133205.617dddd8@kernel.org \
--to=kabel@kernel.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=lorenzo@kernel.org \
--cc=mcroce@microsoft.com \
--cc=netdev@vger.kernel.org \
--cc=sven.auhagen@voleatech.de \
/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).