Re: Weird TCP SACK problem. in Linux...

2006-07-20 Thread Alexey Kuznetsov
Hello! > Hmmm... I dont understand thisso if reording can be detected, (i.e > we use timestamps, DSACK), the dupthreshold is increased Yes. > implementation that might lead to increase in the number of > retransmissions, but leads to improvment in download time Hmm... I thought and still

Re: Weird TCP SACK problem. in Linux...

2006-07-20 Thread Oumer Teyeb
Hi Alexy, Is there anything linux specific about the DSACK implementation that might lead to increase in the number of retransmissions, but leads to improvment in download time when timestamps are not used (and the reverse effect when timestamps are used, less retransmissions but bigger downlo

Re: Weird TCP SACK problem. in Linux...

2006-07-19 Thread Oumer Teyeb
Oumer Teyeb wrote: Hi, Alexey Kuznetsov wrote: Condition triggering start of fast retransmit is the same. The behaviour while retransmit is different. FACKless code behaves more like NewReno. Ok, that is a good point!! Now at least I can convince myself the CDFs for the first retransmiss

Re: Weird TCP SACK problem. in Linux...

2006-07-19 Thread Oumer Teyeb
Hi, Alexey Kuznetsov wrote: Condition triggering start of fast retransmit is the same. The behaviour while retransmit is different. FACKless code behaves more like NewReno. Ok, that is a good point!! Now at least I can convince myself the CDFs for the first retransmissions showing that SAC

Re: Weird TCP SACK problem. in Linux...

2006-07-19 Thread Alexey Kuznetsov
HellO! > IsLost (SeqNum): > This routine returns whether the given sequence number is > considered to be lost. The routine returns true when either > DupThresh discontiguous SACKed sequences have arrived above > 'SeqNum' or (DupThresh * SMSS) bytes with sequence numbers greate

Re: Weird TCP SACK problem. in Linux...

2006-07-19 Thread Oumer Teyeb
Hi , Alexey Kuznetsov wrote: Hello! DSACK) is used, the retransmissions seem to happen earlier . Yes. With SACK/FACK retransmissions can be triggered earlier, if an ACK SACKs a segment which is far enough from current snd.una. That's what happens f.e. in T_SACK_dump5.dat 01:28:15.

Re: Weird TCP SACK problem. in Linux...

2006-07-19 Thread Alexey Kuznetsov
Hello! > DSACK) is used, the retransmissions seem to happen earlier . Yes. With SACK/FACK retransmissions can be triggered earlier, if an ACK SACKs a segment which is far enough from current snd.una. That's what happens f.e. in T_SACK_dump5.dat 01:28:15.681050 < 192.38.55.34.51137 > 192.168.110

Re: Weird TCP SACK problem. in Linux...

2006-07-19 Thread Oumer Teyeb
Hi David, I am using an emualtor that I developed using netfilter (see http://kom.aau.dk/~oumer/publications/VTC05.pdf for a description of the emulator).. and I emualte a UMTS network with RTT of 150ms, and I use a 384kbps connection. There is UMTS frame erasure rate of 10%, but I have persi

Re: Weird TCP SACK problem. in Linux...

2006-07-19 Thread Xiaoliang (David) Wei
Hi Oumer, Your result is interesting. Just a few questions (along with your texts): So I looked further into the results, and what I found was that when SACK (when I refer to SACK here, I mean SACK only without FACK and DSACK) is used, the retransmissions seem to happen earlier . at www.kom

Weird TCP SACK problem. in Linux...

2006-07-18 Thread Oumer Teyeb
Hello Guys, I have some questions regarding TCP SACK implementation in Linux . As I am not a subscriber, could you please cc the reply to me? thanks! I am doing these experiments to find out the impact of reordering. So I have different TCP versions (newReno, SACK, FACk, DSACK, FRTO,) as i