[RFC v2] mac80211: implement eBDP algorithm to fight bufferbloat
johannes at sipsolutions.net
Mon Feb 28 05:07:23 PST 2011
On Mon, 2011-02-21 at 14:06 -0500, John W. Linville wrote:
> > Yeah, I had that idea as well. Could unify the existing skb_orphan()
> > call though :-)
> The one in ieee80211_skb_resize? Any idea how that would look?
Yeah. I think it'd have to be moved out of _skb_resize and made
unconditional in that path, since eventually with this patch you'd do it
> As in my reply to Nathaniel, please notice that the timing estimate
> (and the max_enqueued calculation) only happens for frames that result
> in a tx status report -- at least for now...
> However, if this were generalized beyond mac80211 then we wouldn't
> be able to rely on tx status reports. I can see that dropping frames
> in the driver would lead to timing estimates that would cascade into
> a wide-open queue size. But I'm not sure that would be a big deal,
> since in the long run those dropped frames should still result in IP
> cwnd reductions, etc...?
I don't think we can generically rely on skb_orphan() in the network
stack since that will make socket buffer limits meaningless. In fact, it
pains me a bit that we had to do this in wireless before buffering the
skb, and doing it unconditionally may be worse?
> How do you think the time spent handling URBs in the USB stack relates
> to the time spent transmitting frames? At what point do those SKBs
> get freed?
I honestly don't know. I would hope they are only freed when the URB was
processed (i.e. at least DMA'd to the target device) but I suppose a
driver might also copy the TX frame completely.
> Yeah, I'm still not sure we all have our heads around these issues.
> I mean, on the one hand it seems wrong to limit queueing for one
> stream or station just because some other stream or station is
> higher latency. But on the other hand, it seems to me that those
> streams/stations still have to share the same link and that higher
> real latency for one stream/station could still result in a higher
> perceived latency for another stream/station sharing the same link,
> since they still have to share the same air...no?
Yeah, but retries (robustness) and aggregation (throughput) will
invariably affect latency for everybody else using the shared medium. I
suppose it would be better if queueing would be limited to a certain
amount of air time use *per peer station*, so that each connection can
have fairly low latency. However, this seems much harder to do. But what
could happen here is that bursty traffic to a far-away (slow) station
severely affects latency for and because there's also high traffic to a
closer station that caused a buffering increase.
More information about the Bloat-devel