lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Wed, 17 Mar 2010 13:38:15 +0200 (EET)
From:	"Ilpo Järvinen" <ilpo.jarvinen@...sinki.fi>
To:	raj ravi <mekaviraj@...il.com>
cc:	netdev@...r.kernel.org
Subject: Re: tcp_reordering as 0 possible?

On Mon, 15 Mar 2010, raj ravi wrote:

> what is the behaviour in TCP stack if I set tcp_reordering as 0.
> So , sender will  start retransmission without waiting for any duplicate ACK ?
> /proc/sys/net/ipv4/tcp_reordering   - Please clarify.
> The default value is 3 which means it waits until 3 duplicate ack's
> arrive and then start retransmission.
> 
> "The TCP sender should use the fast retransmit algorithm to detect and
> repair loss based on incoming duplicate ACKs. After the arrival of 3
> duplicate ACKs (4 identical ACKs without the arrival of any other
> intervening packet), TCP performs a retransmission of what appears to
> be the missing segment, without waiting for the retransmission timer
> to expire."

Depends on other things quite much but for a typical transfer you'd still 
need one duplicate ACK to trigger actual recovery. However, in general 
root is not (always) forbidden to set non-sensical values for sysctls.

-- 
 i.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists