[Make-wifi-fast] emulating wifi better - coupling qdiscs in netem?

[dpreed at deepplum.com]

I would toss netem rather than kludging around what appears to be a fundamental design choice made in ins conceptualization. Make a "netem2".
 
FreeBSD has a very nice framework for emulating far more general packet queuing/routing/... in the kernel, called NetGraph. It's incredibly general, and could straightforwardly, with high performance, have modules that do exactly the right emulations of network structures with such blocking, etc. and even random delays.
 
I know this because in my day job at TidalScale, we heavily use NetGraph to implement new very low level protocols, which is pretty straightforward, even including complex multi-adapter adaptive forwarding of our private protocols on 10 and 40 GigE links. Super flexible, entirely in the kernel, running either at real-time priority or not, in a mix.
 
In contrast, the Linux TC framework seems very inflexible, as you've found, in trying to push it to do what it is not designed to do.
 
So tossing netem might be far better. I wonder if NetGraph has ever been ported into some Linux kernel environment...
-----Original Message-----
From: "Dave Taht" <dave.taht at gmail.com>
Sent: Wednesday, May 30, 2018 1:28pm
To: make-wifi-fast at lists.bufferbloat.net
Subject: [Make-wifi-fast] emulating wifi better - coupling qdiscs in netem?



The match to reality of my "wifi slotting" code for netem was so
disappointing that I was extremely reluctant to push support for it up
to mainline iproute2.

I've now spent months failing to come up with something that
could emulate in linux the non-duplex behavior and arbitration steps
that wifi goes through in order to find a new station to transmit to,
or receive from, using netem as a base.

Getting that non-duplex behavior right is the *single most important
thing*, I think, for trying to emulate real wireless behaviors in
real time that I can think of (and to thus be able to run and improve
various e2e transports against it).

A potential tc API seems simple:

tc qdisc add dev veth1 root netem coupled # master (AP)
tc qdisc add dev veth2 root netem couple veth1 # client
tc qdisc add dev veth3 root netme couple veth2 # client

Something more complicated would be to create some sort of
arbitration device and attach that to the qdiscs. (which would make
it more possible to write arbitration devices to emulate lte, gpon,
cable, wireless mesh and other non-duplex behaviors in real time)

But how to convince qdiscs to be arbitrated, only allowing one in a
set to transmit at the same time? (and worse, in the long run,
allowing MU-MIMO-like behaviors).

I'm tempted to *not* put my failed thinking down here in the hope that
someone says, out there, "oh, that's easy, just create this structure
with X API call and use Y function and you're clear of all the
potential deadlock and RCU issues, and we've been doing that for
years, you idiot! Here's the code for how we do it, sorry we didn't
submit it earlier."

What I thought (*and still think*) is of creating a superset of the
qdisc_watchdog_schedule_ns() function is a start at it:

tag = qdisc_watchdog_create_arb("some identifier");
qdisc_watchdog_schedule_arb(nsec, tag); /* null tag = schedule_ns */

which doesn't allow that qdisc instance to be run until the arbitrator
says it can run (essentially overriding the timeout specified)

But I actually wouldn't mind something that worked at the veth, or
device, rather than qdisc level...

thoughts?

PS I just spent several days working on another aspect of the problem,
which is replaying delay distributions (caused by interference and
such)... and that, sigh, to me, also belongs in some sort of
arbitration device rather than directly in netem. Maybe tossing netem
entirely is the answer. I don't know.

-- 

Dave Täht
CEO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-669-226-2619
_______________________________________________
Make-wifi-fast mailing list
Make-wifi-fast at lists.bufferbloat.net
https://lists.bufferbloat.net/listinfo/make-wifi-fast
-- 
Reed Online Ltd is a company registered in England and Wales. Company 
Registration Number: 6317279.Registered Office: Academy Court, 94 Chancery 
Lane, London WC2A 1DT.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.bufferbloat.net/pipermail/make-wifi-fast/attachments/20180530/7fd8fd64/attachment.html>