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

2007-04-30 Thread David Miller
From: "Ilpo_Järvinen" <[EMAIL PROTECTED]> 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. RFC4

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

2007-04-13 Thread Ilpo Järvinen
Since you did update the abstraction part too (which I wasn't expecting). Here's the update version so that you don't have to resolve it. [PATCH] [TCP] FRTO: RFC4138 allows Nagle override when new data must be sent This is a corner case where less than MSS sized new data thingie is awaiting in

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

2007-04-11 Thread Ilpo Järvinen
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