From: Stephen Hemminger <shemminger@osdl.org>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tcp: limit window scaling if window is clamped
Date: Fri, 18 Aug 2006 20:03:23 -0700 [thread overview]
Message-ID: <20060818200323.40b1a74a@localhost.localdomain> (raw)
In-Reply-To: <20060818.170030.74563682.davem@davemloft.net>
On Fri, 18 Aug 2006 17:00:30 -0700 (PDT)
David Miller <davem@davemloft.net> wrote:
> From: Stephen Hemminger <shemminger@osdl.org>
> Date: Fri, 18 Aug 2006 10:29:38 -0700
>
> > This small change allows for easy per-route workarounds for broken hosts or
> > middleboxes that are not compliant with TCP standards for window scaling.
> > Rather than having to turn off window scaling globally. This patch allows
> > reducing or disabling window scaling if window clamp is present.
> >
> > Example: Mark Lord reported a problem with 2.6.17 kernel being unable to
> > access http://www.everymac.com
> >
> > # ip route add 216.145.246.23/32 via 10.8.0.1 window 65535
> >
> > I would argue this ought to go in stable kernel as well.
> >
> > Signed-off-by: Stephen Hemminger <shemminger@osdl.org>
>
> I want to think about this some more, it might have unintended
> consequences. I really am not all that thrilled about putting in
> workaround for this problem especially if it hurts a legitimate use of
> some kind.
I was going for the least impact workaround using existing mechanisms.
There already is a way to set metrics per route. The code already limits
the window scale to the maximum possible window based on tcp memory limit
so it made sense to clamp based on congestion window as well.
It didn't make sense to add a new metric.
next prev parent reply other threads:[~2006-08-19 3:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-18 17:29 [PATCH] tcp: limit window scaling if window is clamped Stephen Hemminger
2006-08-19 0:00 ` David Miller
2006-08-19 3:03 ` Stephen Hemminger [this message]
2006-08-22 7:07 ` David 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=20060818200323.40b1a74a@localhost.localdomain \
--to=shemminger@osdl.org \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--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).