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 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. > > And yeah, I'd also be happy to discuss what it would take to make a > native XDP implementation of the OVS datapath; including what (if > anything) is missing from the current XDP feature set to make this > feasible. I must admit that I'm not quite clear on why that wasn't the > approach picked for the first attempt to speed up OVS using XDP... > > -Toke >
