On Sun, 17 Nov 2013, Anoop Ghanwani wrote:
This should give you an idea of the kind of buffering that is actually available. As port-counts go up, the amount of buffering per port goes down. http://people.ucsc.edu/~warner/buffer.html
Not only that, but some switches actually have shared buffer space for some or all ports, so if one port is congested, you can get immediate drops on other ports because of lack of buffer space.
For the simulations to be relevant for such switches, they would have to be done with significantly smaller buffer sizes. The sizing gets even worse when we consider there may be multiple priorities and some of those may be lossless (requiring dedicated buffers be set aside for them).
For instance, I have a switch at home with 24 gig ports that have 128 kilobytes of memory total, shared for the entire switch for all ports. It's a really cheap one, but still meant for enterprise deployment.
How would we model something like that? Guess it won't add much to bufferbloat so perhaps moot discussion :) -- Mikael Abrahamsson email: [email protected] _______________________________________________ aqm mailing list [email protected] https://www.ietf.org/mailman/listinfo/aqm
