Abraham van der Merwe writes: > Hi Don! > > > > I then tried fifos. With small packet fifos the packet loss is just > > > to great to be of any use and even then the latency is quite high (~200ms). A small detail: what are "small packet fifos"? You mean fifos that can only hold a small number of packets? Or fifos that only hold packets with small numbers of bytes? > > You consider 200ms high? One max size packet = 1500 bytes = 12Kbit > > which is about 200ms on a 64Kbit link. You can't expect to do better. > > The problem is that with 200ms the packet loss is so much that the link is > effectively useless (90% packet loss). As soon as I make the queue big > enough to not drop significant amounts of packets, the latency goes way up > (>3 secs). I don't understand the connection between 200ms and packet loss. If you make the queue small (in packet capacity) then worst case latency decreases. Packet loss occurs in either case whenever a packet arrives and the queue is full. If you try to send at a higher rate than allowed then you will fill the queue in either case (a small queue more quickly, of course), and from then on you will lose packets. If you send packets at twice the allowed rate you lose half of them, if you send at 10 times the allowed rate you lose 90%. The fact that you're losing lots of packets, though, indicates to me that you're acting like an attacker, and dropping most of that traffic is therefore exactly the right thing to do. If you were using a correctly working tcp it would not continue to send at 10 times the allowed rate. It would notice that packets were being lost and would slow down until the loss rate became very small. Similarly, I don't understand the latency issue. An application that cares about latency will not create a large backlog. What is this application that is sending faster than the link allows and wants a low latency, and why is it misbehaving? _______________________________________________ LARTC mailing list / LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
