From: John Heffner <jheffner@psc.edu>
To: "Ilpo Järvinen" <ilpo.jarvinen@helsinki.fi>
Cc: David Miller <davem@davemloft.net>, netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH] fix limited slow start bug
Date: Thu, 22 Feb 2007 16:52:03 -0500 [thread overview]
Message-ID: <45DE1083.6040900@psc.edu> (raw)
In-Reply-To: <Pine.LNX.4.64.0702222317000.29273@kivilampi-30.cs.helsinki.fi>
Ilpo Järvinen wrote:
> BTW, while looking this patch, I noticed that snd_cwnd_clamp is only u16
> while snd_cwnd is u32, which seems rather strange since snd_cwnd is being
> limited by the clamp value here and there?!?! And tcp_highspeed.c is
> clearly assuming even more than this (but the problem is hidden as
> snd_cwnd_clamp is feed back to the min_t and the used 32-bit constant
> could be safely cut to 16-bits anyway):
>
> tp->snd_cwnd_clamp = min_t(u32, tp->snd_cwnd_clamp, 0xffffffff/128);
>
> Has the type being changed somewhere in the past or why is this so?
It's been that way as long as I can remember. It's always been a
mystery to me as well. I suspect the tcp_highspeed code is that way
because this patch originally came out of the Web100-patched kernel,
which at one point was using a 32 bit snd_cwnd_clamp IIRC.
I think it's not unreasonable to change clamp to 32 bits now, since with
1500 byte packets, this corresponds to a max cwnd of ~94MB. This is
pretty big, but we are currently right at this limit with 10 GigE.
-John
next prev parent reply other threads:[~2007-02-22 21:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-22 18:56 [PATCH] fix limited slow start bug John Heffner
2007-02-22 21:37 ` Ilpo Järvinen
2007-02-22 21:52 ` John Heffner [this message]
2007-02-23 6:53 ` David Miller
2007-02-23 6:42 ` David Miller
-- strict thread matches above, loose matches on Subject: below --
2007-02-25 8:55 Roger While
2007-02-25 23:43 ` David Miller
2007-02-26 2:19 ` Arnaldo Carvalho de Melo
2007-02-26 3:02 ` Arnaldo Carvalho de Melo
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=45DE1083.6040900@psc.edu \
--to=jheffner@psc.edu \
--cc=davem@davemloft.net \
--cc=ilpo.jarvinen@helsinki.fi \
--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).