From: David Miller <davem@davemloft.net>
To: angelo.castellani@gmail.com
Cc: netdev@vger.kernel.org, andrea.baiocchi@uniroma1.it,
francesco@net.infocom.uniroma1.it
Subject: Re: [PATCH 2/2][TCP] YeAH-TCP: limited slow start exported function
Date: Thu, 22 Feb 2007 00:21:47 -0800 (PST) [thread overview]
Message-ID: <20070222.002147.10299202.davem@davemloft.net> (raw)
In-Reply-To: <45D97D5D.9040101@gmail.com>
From: "Angelo P. Castellani" <angelo.castellani@gmail.com>
Date: Mon, 19 Feb 2007 11:35:09 +0100
> From: Angelo P. Castellani <angelo.castellani@gmail.con>
>
> RFC3742: limited slow start
>
> See http://www.ietf.org/rfc/rfc3742.txt
>
> Signed-off-by: Angelo P. Castellani <angelo.castellani@gmail.con>
> ---
>
> To allow code reutilization I've added the limited slow start procedure
> as an exported symbol of linux tcp congestion control.
>
> On large BDP networks canonical slow start should be avoided because it
> requires large packet losses to converge, whereas at lower BDPs slow
> start and limited slow start are identical. Large BDP is defined through
> the max_ssthresh variable.
>
> I think limited slow start could safely replace the canonical slow start
> procedure in Linux.
...
> p.s.: in the attached patch is added an exported function currently used
> only by YeAH TCP
Please never submit patches like this, submit the infrastructure
FIRST, then submit the stuff that uses it. When a sequence of patches
is applied, in sequence, the tree should build properly (even with all
available new options enabled) at each step along the way.
Otherwise we have the situation we have now, in that YeaH is in my
tree but doesn't build successfully.
What I'm going to do to "fix" this, is yank YeaH implementation out
of my tree, add this second patch first, then add the YeaH patch
back.
Please never do this again.
next prev parent reply other threads:[~2007-02-22 8:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-19 10:35 [PATCH 2/2][TCP] YeAH-TCP: limited slow start exported function Angelo P. Castellani
2007-02-19 10:36 ` Angelo P. Castellani
2007-02-19 21:00 ` John Heffner
2007-02-19 23:50 ` Angelo P. Castellani
2007-02-20 4:32 ` John Heffner
2007-02-20 9:20 ` Angelo P. Castellani
2007-02-22 8:27 ` David Miller
2007-02-22 8:32 ` David Miller
2007-02-22 14:25 ` John Heffner
2007-02-22 14:37 ` David Miller
2007-02-22 8:21 ` David Miller [this message]
2007-02-22 16:08 ` Angelo P. Castellani
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=20070222.002147.10299202.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=andrea.baiocchi@uniroma1.it \
--cc=angelo.castellani@gmail.com \
--cc=francesco@net.infocom.uniroma1.it \
--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).