On Tue, 16 Aug 2022 08:29:04 +0000 Bobby Eshleman wrote: > > We've been burnt in the past by people doing the "let me just pick > > these useful pieces out of netdev" thing. Makes life hard both for > > maintainers and users trying to make sense of the interfaces. > > > > What comes to mind if you're just after queuing is that we already > > bastardized the CoDel implementation (include/net/codel_impl.h). > > If CoDel is good enough for you maybe that's the easiest way? > > Although I suspect that you're after fairness not early drops. > > Wireless folks use CoDel as a second layer queuing. (CC: Toke) > > That is certainly interesting to me. Sitting next to "codel_impl.h" is > "include/net/fq_impl.h", and it looks like it may solve the datagram > flooding issue. The downside to this approach is the baking of a > specific policy into vsock... which I don't exactly love either. > > I'm not seeing too many other of these qdisc bastardizations in > include/net, are there any others that you are aware of? Just what wireless uses (so codel and fq as you found out), nothing else comes to mind. > > Eh, I was hoping it was a side channel of an existing virtio_net > > which is not the case. Given the zero-config requirement IDK if > > we'll be able to fit this into netdev semantics :( > > It's certainly possible that it may not fit :/ I feel that it partially > depends on what we mean by zero-config. Is it "no config required to > have a working socket" or is it "no config required, but also no > tuning/policy/etc... supported"? The value of tuning vs confusion of a strange netdev floating around in the system is hard to estimate upfront. The nice thing about using a built-in fq with no user visible knobs is that there's no extra uAPI. We can always rip it out and replace later. And it shouldn't be controversial, making the path to upstream smoother.
