From: Andrea Arcangeli <andrea@suse.de>
To: "David S. Miller" <davem@redhat.com>
Cc: ak@suse.de, kuznet@ms2.inr.ac.ru, linux-kernel@vger.kernel.org
Subject: Re: 2.4 delayed acks don't work, fixed
Date: Wed, 19 Mar 2003 20:48:59 +0100 [thread overview]
Message-ID: <20030319194859.GO30541@dualathlon.random> (raw)
In-Reply-To: <20030318.180219.91189534.davem@redhat.com>
On Tue, Mar 18, 2003 at 06:02:19PM -0800, David S. Miller wrote:
> TCP needs at least a full window of data on the send side to clock
> things properly. This streamer application doesn't give TCP that
the inflating doubling the ato is too slow after you destroyed the ato
info setting it to 4 this is why it takes so long for 2.4 to clock
things properly, at least you should inflate it with the average down.
the <= in the window raise check in recvmsg as well generate window
updates too early, I find better to wait two packets to be read before
sending the window update. Now that I understood better how the logic in
mainline works I'll try to make a better patch (not very soon though
since I'm busy with other stuff and next week I'll be offline most of
the time).
Andrea
prev parent reply other threads:[~2003-03-19 19:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-17 8:25 2.4 delayed acks don't work, fixed Andrea Arcangeli
2003-03-18 18:34 ` kuznet
2003-03-18 19:34 ` Andrea Arcangeli
2003-03-18 20:13 ` kuznet
2003-03-18 22:19 ` Andrea Arcangeli
2003-03-18 22:35 ` kuznet
[not found] ` <20030319002409.GI30541@dualathlon.random>
2003-03-19 0:37 ` David S. Miller
2003-03-19 0:58 ` Andrea Arcangeli
2003-03-19 1:33 ` Help with patch for vesafbd support again? Kendall Bennett
2003-03-19 3:00 ` Randy.Dunlap
2003-03-19 19:25 ` Kendall Bennett
2003-03-19 1:55 ` 2.4 delayed acks don't work, fixed Andi Kleen
2003-03-19 2:02 ` David S. Miller
2003-03-19 19:48 ` Andrea Arcangeli [this message]
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=20030319194859.GO30541@dualathlon.random \
--to=andrea@suse.de \
--cc=ak@suse.de \
--cc=davem@redhat.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@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