netdev - Re: [PATCH 2/2] [TCP] FRTO: RFC4138 allows Nagle override when new data must be sent

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 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Date:	Mon, 30 Apr 2007 00:42:25 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	ilpo.jarvinen@...sinki.fi
Cc:	netdev@...r.kernel.org
Subject: Re: [PATCH 2/2] [TCP] FRTO: RFC4138 allows Nagle override when new
 data must be sent

From: "Ilpo_Järvinen" <ilpo.jarvinen@...sinki.fi>
Date: Wed, 11 Apr 2007 12:24:04 +0300

> This is a corner case where less than MSS sized new data thingie
> is awaiting in the send queue. For F-RTO to work correctly, a
> new data segment must be sent at certain point or F-RTO cannot
> be used at all. RFC4138 allows overriding of Nagle at that
> point.
> 
> Implementation uses frto_counter states 2 and 3 to distinguish
> when Nagle override is needed.
> 
> Signed-off-by: Ilpo Järvinen <ilpo.jarvinen@...sinki.fi>

Also applied, thanks a lot.
-
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