On 19/10/24 (木) 19:13:09, Toke Høiland-Jørgensen wrote:
John Fastabend <john.fastabend@xxxxxxxxx> writes:
Toke Høiland-Jørgensen wrote:
John Fastabend <john.fastabend@xxxxxxxxx> writes:
I think for sysadmins in general (not OVS) use case I would work
with Jesper and Toke. They seem to be working on this specific
problem.
We're definitely thinking about how we can make "XDP magically speeds up
my network stack" a reality, if that's what you mean. Not that we have
arrived at anything specific yet...
There seemed to be two thoughts in the cover letter one how to make
OVS flow tc path faster via XDP. And the other how to make other users
of tc flower software stack faster.
For the OVS case seems to me that OVS should create its own XDP
datapath if its 5x faster than the tc flower datapath. Although
missing from the data was comparing against ovs kmod so that
In the cover letter there is
xdp_flow TC ovs kmod
-------- -------- --------
5.2 Mpps 1.2 Mpps 1.1 Mpps
Or are you talking about something different?
comparison would also be interesting. This way OVS could customize
things and create only what they need.
But the other case for a transparent tc flower XDP a set of user tools
could let users start using XDP for this use case without having to
write their own BPF code. Anyways I had the impression that might be
something you and Jesper are thinking about, general usability for
users that are not necessarily writing their own network.
Yeah, you are right that it's something we're thinking about. I'm not
sure we'll actually have the bandwidth to implement a complete solution
ourselves, but we are very much interested in helping others do this,
including smoothing out any rough edges (or adding missing features) in
the core XDP feature set that is needed to achieve this :)
I'm very interested in general usability solutions.
I'd appreciate if you could join the discussion.
Here the basic idea of my approach is to reuse HW-offload infrastructure
in kernel.
Typical networking features in kernel have offload mechanism (TC flower,
nftables, bridge, routing, and so on).
In general these are what users want to accelerate, so easy XDP use also
should support these features IMO. With this idea, reusing existing
HW-offload mechanism is a natural way to me. OVS uses TC to offload
flows, then use TC for XDP as well...
Of course as John suggested there are other ways to do that. Probably we
should compare them more thoroughly to discuss it more?
Toshiaki Makita
