From: Rick Jones <rick.jones2@hp.com>
To: Alexey Kuznetsov <kuznet@ms2.inr.ac.ru>
Cc: Alexander Vodomerov <alex@sectorb.msk.ru>,
netdev@vger.kernel.org, davem@davemloft.net
Subject: Re: [PATCH][RFC] Re: high latency with TCP connections
Date: Tue, 05 Sep 2006 10:55:16 -0700 [thread overview]
Message-ID: <44FDBA04.3080104@hp.com> (raw)
In-Reply-To: <20060904160045.GA15599@ms2.inr.ac.ru>
Alexey Kuznetsov wrote:
> Hello!
>
>
>>Some people reported that this program runs in 9.997 sec when run on
>>FreeBSD.
>
>
> Try enclosed patch. I have no idea why 9.997 sec is so magic, but I
> get exactly this number on my notebook. :-)
>
> Alexey
>
> =================
>
> This patch enables sending ACKs each 2d received segment.
> It does not affect either mss-sized connections (obviously) or connections
> controlled by Nagle (because there is only one small segment in flight).
>
> The idea is to record the fact that a small segment arrives
> on a connection, where one small segment has already been received
> and still not-ACKed. In this case ACK is forced after tcp_recvmsg()
> drains receive buffer.
>
> In other words, it is a "soft" each-2d-segment ACK, which is enough
> to preserve ACK clock even when ABC is enabled.
Is this really necessary? I thought that the problems with ABC were in
trying to apply byte-based heuristics from the RFC(s) to a
packet-oritented cwnd in the stack?
rick jones
next prev parent reply other threads:[~2006-09-05 17:55 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-30 10:07 high latency with TCP connections Alexander Vodomerov
2006-08-30 17:27 ` Stephen Hemminger
2006-08-30 21:39 ` David Miller
2006-08-30 22:04 ` Stephen Hemminger
2006-08-30 23:00 ` Rick Jones
2006-08-31 8:14 ` Alexander Vodomerov
2006-08-31 15:44 ` Sridhar Samudrala
2006-08-31 18:22 ` Kelly Burkhart
2006-08-31 19:40 ` Rick Jones
2006-08-31 21:08 ` Ian McDonald
2006-08-31 21:46 ` Alexey Kuznetsov
2006-08-31 22:14 ` Stephen Hemminger
2006-08-31 22:44 ` David Miller
2006-08-31 23:29 ` Alexey Kuznetsov
2006-08-31 23:57 ` David Miller
2006-09-01 3:23 ` Stephen Hemminger
2006-09-01 3:39 ` Ian McDonald
2006-09-01 6:23 ` David Miller
2006-09-01 9:44 ` Pekka Savola
2006-09-01 9:49 ` David Miller
2006-09-01 9:47 ` Alexey Kuznetsov
2006-09-01 11:00 ` Evgeniy Polyakov
[not found] ` <20060901090046.69b3d583@localhost.localdomain>
2006-09-01 20:55 ` [PATCH] tcp: turn ABC off Stephen Hemminger
2006-09-02 7:22 ` Evgeniy Polyakov
2006-09-02 8:10 ` Herbert Xu
2006-09-04 9:10 ` high latency with TCP connections Alexey Kuznetsov
2006-09-04 16:00 ` [PATCH][RFC] " Alexey Kuznetsov
2006-09-05 17:55 ` Rick Jones [this message]
2006-09-05 22:13 ` Alexey Kuznetsov
2006-09-18 7:39 ` David Miller
2006-09-18 17:11 ` Rick Jones
2006-09-18 20:41 ` Alexey Kuznetsov
2006-09-18 21:24 ` Rick Jones
2006-09-18 22:51 ` Alexey Kuznetsov
2006-09-19 0:37 ` Rick Jones
2006-09-22 13:46 ` Alexey Kuznetsov
2006-09-22 17:15 ` Rick Jones
2006-09-18 7:31 ` David Miller
2006-09-18 10:37 ` Alexey Kuznetsov
2006-09-18 13:56 ` David Miller
2006-09-20 22:44 ` Stephen Hemminger
2006-09-20 22:47 ` David Miller
2006-09-20 22:55 ` Stephen Hemminger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=44FDBA04.3080104@hp.com \
--to=rick.jones2@hp.com \
--cc=alex@sectorb.msk.ru \
--cc=davem@davemloft.net \
--cc=kuznet@ms2.inr.ac.ru \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).