From: Alan <alan@lxorguk.ukuu.org.uk>
To: eli@dev.mellanox.co.il
Cc: eli@dev.mellanox.co.il, linux-kernel@vger.kernel.org,
linux-net@vger.kernel.org
Subject: Re: UDP packets loss
Date: Thu, 16 Nov 2006 23:52:23 +0000 [thread overview]
Message-ID: <20061116235223.78f13473@localhost.localdomain> (raw)
In-Reply-To: <18154.194.90.237.34.1163703097.squirrel@dev.mellanox.co.il>
On Thu, 16 Nov 2006 20:51:37 +0200 (IST)
eli@dev.mellanox.co.il wrote:
> eventually slow the whole thing to a rate such all parts can handle. But
> is there a way to overcome this situation and to avoid packets drop? If
> this would happen then TCP would work at higher rates as well?? Perhaps
> increase buffers sizes?
Increased buffer sizes can actually paradoxically make the situation
worse. Van Jacobson once claimed that those who do not understand TCP are
doomed to re-invent it.
If you have a very controlled environment then there are alternative flow
control approaches including counting approaches when you know the
underlying transport is basically reliable (or you can tolerate minor
loss). That's roughly speaking the equivalent of TCP with fixed windows
and knowing that the buffering worst cases are the end points.
Alan
next prev parent reply other threads:[~2006-11-16 23:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <60157.89.139.64.58.1163542548.squirrel@dev.mellanox.co.il>
2006-11-16 18:51 ` UDP packets loss eli
2006-11-16 19:01 ` John Heffner
2006-11-16 21:10 ` eli
2006-11-16 21:23 ` David Miller
2006-11-16 23:52 ` Alan [this message]
2006-11-17 14:48 ` Neil Horman
2006-11-14 22:15 eli
2006-11-14 22:35 ` Stephen Hemminger
2006-11-14 23:08 ` eli
2006-11-14 23:23 ` Stephen Hemminger
2006-11-15 13:03 ` Neil Horman
2006-11-14 23:14 ` Auke Kok
2006-11-15 21:57 ` John Heffner
2006-11-14 22:54 ` Richard B. Johnson
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=20061116235223.78f13473@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=eli@dev.mellanox.co.il \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@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