From: Mark Lord <lkml@rtr.ca>
To: John Heffner <jheffner@psc.edu>
Cc: Linus Torvalds <torvalds@osdl.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
netdev@vger.kernel.org, davem@davemloft.net
Subject: Re: 2.6.17: networking bug??
Date: Tue, 13 Jun 2006 14:26:12 -0400 [thread overview]
Message-ID: <448F0344.9000008@rtr.ca> (raw)
In-Reply-To: <Pine.LNX.4.64.0606131048550.5498@g5.osdl.org>
Linus Torvalds wrote:
>
> On Tue, 13 Jun 2006, John Heffner wrote:
>> The best thing you can do is try to find this broken box and inform its owner
>> that it needs to be fixed. (If you can find out what it is, I'd be interested
>> to know.) In the meantime, disabling window scaling will work around the
>> problem for you.
>
> Well, arguably, we shouldn't necessarily have defaults that use window
> scaling, or we should have ways to recognize automatically when it
> doesn't work (which may not be possible).
>
> It's not like there aren't broken boxes out there, and it might be better
> to make the default buffer sizes just be low enough that window scaling
> simply isn't an issue.
>
> I suspect that the people who really want/need window scaling know about
> it, and could be assumed to know enough to raise their limits, no?
Agreed. It's taken me over a month here to realize that the particular
webserver in question (www.everymac.com) wasn't "dead", but merely being
blocked by my 2.6.17 kernel. All was fine with 2.6.16, as I discovered today.
I wonder how many other "dead sites" there are out there,
that will be shut off from people when they "upgrade" to 2.6.17 ?
I'm a kernel hacker. Most users of 2.6.17 will not be.
The default should be something that works "by default".
Cheers
next prev parent reply other threads:[~2006-06-13 18:26 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-13 14:08 2.6.17: networking bug?? Mark Lord
2006-06-13 14:26 ` Mark Lord
2006-06-13 15:00 ` Mark Lord
2006-06-13 15:28 ` Mark Lord
2006-06-13 16:58 ` Mark Lord
2006-06-13 17:22 ` Mark Lord
2006-06-13 17:39 ` John Heffner
2006-06-13 17:50 ` Linus Torvalds
2006-06-13 18:26 ` Mark Lord [this message]
2006-06-13 19:08 ` Mark Lord
2006-06-13 21:26 ` David Miller
2006-06-13 21:49 ` Mark Lord
2006-06-13 22:12 ` Rick Jones
2006-06-13 22:23 ` David Miller
2006-06-13 22:40 ` Rick Jones
2006-06-13 23:01 ` David Miller
2006-06-14 1:25 ` John Heffner
2006-06-13 23:22 ` Matt Mackall
2006-06-19 7:07 ` Helge Hafting
2006-06-14 5:18 ` Andi Kleen
2006-06-14 8:09 ` Daniel Drake
2006-06-13 18:28 ` John Heffner
2006-06-13 20:45 ` Barry K. Nathan
2006-06-13 22:09 ` Chase Venters
2006-06-13 22:23 ` David Miller
2006-07-02 17:39 ` Jan Knutar
2006-06-19 6:57 ` Helge Hafting
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=448F0344.9000008@rtr.ca \
--to=lkml@rtr.ca \
--cc=davem@davemloft.net \
--cc=jheffner@psc.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=torvalds@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.