From: "David S. Miller" <davem@redhat.com>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: netdev@oss.sgi.com
Subject: Re: [PATCH] unclamp tcp receive window if doing dynamic receive sizing
Date: Mon, 7 Jun 2004 16:17:41 -0700 [thread overview]
Message-ID: <20040607161741.1f295aca.davem@redhat.com> (raw)
In-Reply-To: <20040607133056.5ab9e72d@dell_ss3.pdx.osdl.net>
On Mon, 7 Jun 2004 13:30:56 -0700
Stephen Hemminger <shemminger@osdl.org> wrote:
> When running tests over higher speed links, the new 2.6 Dynamic Receiver Sizing
> code doesn't increase the window large enough. The problem is that the window
> clamp restricts the allowed window to the socket receive buffer size (85k)
>
> Easiest fix is to not restrict window clamp if we want to dynamic receiver stuff.
> This is what web100 did.
>
> Thanks to John Heffner for finding this.
This turns off all tcp_app_win semantics, are you sure that
tcp_app_win makes no sense when doing dynamic receive buffer
sizing? I think we should still factor it in, perhaps dynamically,
during rcvbuf growth.
next prev parent reply other threads:[~2004-06-07 23:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-07 20:30 [PATCH] unclamp tcp receive window if doing dynamic receive sizing Stephen Hemminger
2004-06-07 23:17 ` David S. Miller [this message]
2004-06-11 4:54 ` David S. Miller
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=20040607161741.1f295aca.davem@redhat.com \
--to=davem@redhat.com \
--cc=netdev@oss.sgi.com \
--cc=shemminger@osdl.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).