[Cake] ER-X now running cake, thanks for the help. :)

Neil Shepperd nshepperd at gmail.com
Fri May 5 15:29:06 EDT 2017


Shouldn't unresponsive UDP flows be punished for sending too many packets?
In that case if there's any problem at all it is that the packets get
through with 20 seconds delay instead of being dropped entirely. Although
it shouldn't really matter either way as long as other flows are not
unfairly impacted.

On Fri, 5 May 2017 at 13:12 <erik.taraldsen at telenor.com> wrote:

> > Fra: Toke Høiland-Jørgensen <toke at toke.dk>
> >
> > Right, so you're measuring the actual latency experienced by the UDP
> packets in the
> > unresponsive flow? Yeah, you'll get quite a bit of latency in that case.
> But not sure that's a case
> > we should be optimising for...
>
> That was just the worst case scenario, not really meant to emulate user
> traffic.  And I'm not suggesting that the schedulers should be optimized
> for that. But we can agree that 20+ seconds of delay is a bit much no
> matter how it is measured? :)
>
> I also use nuttcp to model other kinds of traffic, such as VIOP, Voice
> over WiFi, dumb udp vod that Telenor uses.  Then I subject the router to
> various kinds of line saturation and stress.  Cloud upload, torrent, virus
> emulation (zmap not really designed for that, but man, if you want to
> inflict pain on a router... zmap is your daddy).  And we try to make sure
> that long living tcp/vpn sessions are not torn down due to need for more
> sessions in nat for yet another torrent session.  Different QoS/schedulers
> behave different and we try and use the best possible solution for a given
> HW/access tech.  What works very well for balancing cloud upload and
> interactive traffic like ssh or http may fail miserably on torrent.  And
> the other way around.  On our legacy stuff we can't implement fq_codel,
> cake or sfq even.
>
> And as you know I also incorporate flent.
>
>
> -Erik
> _______________________________________________
> Cake mailing list
> Cake at lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cake
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.bufferbloat.net/pipermail/cake/attachments/20170505/999b8b8d/attachment.html>


More information about the Cake mailing list