On Thu, Jul 11, 2013 at 9:54 AM, Kathleen Nichols nich...@pollere.com wrote:
Yes. I think that's a sort of application - dependent bit of code perhaps.
Van and I had various discussions about this and put that in with very
low bandwidth applications in mind, where some maximums might
be much
On Thu, 2013-07-11 at 10:09 -0700, Dave Taht wrote:
In my default environments (wifi, mainly) the hardware queues have
very different properties.
I'm under the impression that in at least a few ethernet devices they
are essentially the same. That said, in the sch_mq case, an entirely
On Thu, Jul 11, 2013 at 10:44 AM, Eric Dumazet eric.duma...@gmail.com wrote:
On Thu, 2013-07-11 at 10:09 -0700, Dave Taht wrote:
In my default environments (wifi, mainly) the hardware queues have
very different properties.
I'm under the impression that in at least a few ethernet devices they
My results with netem were generally so dismal that I'd abandoned it.
I just finished building a bunch of kernels from net-next with eric's
improvements to it, so I'm about to try it again.
My intent is to duplicate most of the RTTs cablelabs simulated with,
under essentially the same workloads,
On Thu, 2013-07-11 at 14:18 -0700, Dave Taht wrote:
I have incidentally long thought that you are also tweaking target and
interval for your environment?
Google data centers are spread all over the world, and speed of light
was not increased by wonderful Google engineers,
thats a real pity I
