From: Andi Kleen <ak@suse.de>
To: manfred@colorfullife.com
Cc: ak@suse.de, davem@redhat.com, linux-kernel@vger.kernel.org,
kuznet@ms2.inr.ac.ru
Subject: Re: Linux 2.2.16 through 2.2.18preX TCP hang bug triggered by rsync
Date: Thu, 25 Jan 2001 13:34:29 +0100 [thread overview]
Message-ID: <20010125133429.A17285@gruyere.muc.suse.de> (raw)
In-Reply-To: <3A701AEB.CF4CE9C3@stud.uni-saarland.de>
In-Reply-To: <3A701AEB.CF4CE9C3@stud.uni-saarland.de>; from masp0008@stud.uni-sb.de on Thu, Jan 25, 2001 at 12:24:11PM +0000
On Thu, Jan 25, 2001 at 12:24:11PM +0000, Studierende der Universitaet des Saarlandes wrote:
> Andi wrote:
> > Basically it would accept the acks with the data in most
> > cases except when the application has totally stopped
> > reading and in that case it doesn't harm to ignore the
> > acks.
>
> But it seems that that's exactly what rsync does:
> It performs bulk data writes without reading. There are 32 kB in the
> receive buffers, and rsync continues to write. If the process would read
> some data the TCP stack would immediately recover.
Yes, but it has 64K of buffer. The other 32K are for skb headers. When it is
sending MTU sized packets (and the MTU has any reasonable value) then most
of the other 32K are empty (a skb has ~150 bytes overhead) and you could
fit a few such bogus acks with data into that.
> RST are already processed, ACK's should be processed, but what about
> URG?
Nobody cares about URG, it is broken anyways ;)
-Andi
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-25 12:35 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-25 12:24 Studierende der Universitaet des Saarlandes
2001-01-25 12:34 ` Andi Kleen [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-01-26 20:56 Dave Dykstra
2001-01-27 18:27 ` kuznet
2001-01-23 22:17 Manfred Spraul
2001-01-23 22:59 ` Manfred Spraul
2001-01-24 20:03 ` kuznet
2001-01-24 20:34 ` Manfred Spraul
2001-01-24 20:42 ` kuznet
2001-01-25 18:35 ` kuznet
2001-01-24 20:56 ` Andi Kleen
2001-01-25 10:58 ` Matthias Andree
2001-01-25 12:17 ` James Sutherland
2001-01-25 12:27 ` Matthias Andree
2001-01-25 11:32 ` David S. Miller
2001-01-25 11:40 ` Andi Kleen
2001-01-25 11:44 ` David S. Miller
2001-01-25 11:56 ` Andi Kleen
2001-01-25 12:25 ` James Sutherland
2001-01-23 20:42 Dave Dykstra
2001-01-23 22:51 ` Dave Dykstra
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=20010125133429.A17285@gruyere.muc.suse.de \
--to=ak@suse.de \
--cc=davem@redhat.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=manfred@colorfullife.com \
/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
all inboxes | Powered by JetHome®