All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Drake <dsd@gentoo.org>
To: Mark Lord <lkml@rtr.ca>
Cc: John Heffner <jheffner@psc.edu>,
	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: Wed, 14 Jun 2006 09:09:13 +0100	[thread overview]
Message-ID: <448FC429.4060004@gentoo.org> (raw)
In-Reply-To: <448F0D4B.30201@rtr.ca>

Mark Lord wrote:
> Further to this, the current behaviour is badly unpredictable.
> 
> A machine could be working perfectly, not (noticeably) affected
> by this bug.  And then the user adds another stick of RAM to it.

This "bug" already existed in 2.6.16 to a certain extent: you were 
losing out on a lot of TCP performance. Go back to 2.6.7, measure TCP 
performance, and you'll probably find it was significantly better.

Also, there aren't that many broken end-points out there. 
www.everymac.com loads fine for me and does not ignore the window scale 
factor.

The problem in your case is a broken router in the middle. I had the 
same problem: certain sites would not load, but there is absolutely 
nothing wrong with the servers that run these sites:

http://marc.theaimsgroup.com/?l=linux-netdev&m=114478312100641&w=2

I contacted my ISP and informed them of the issue. They fixed it 
nationwide within a few weeks. You might try confirming that your 
problem only applies to HTTP like mine did (ISP runs some lame 
transparent webcaches), and it was a bug in the software there (NetApp).

We already had the "some routers are broken, should we do anything" 
discussion back at the time of 2.6.8:

http://lwn.net/Articles/92727/

Daniel


  parent reply	other threads:[~2006-06-14  8:07 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
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 [this message]
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=448FC429.4060004@gentoo.org \
    --to=dsd@gentoo.org \
    --cc=davem@davemloft.net \
    --cc=jheffner@psc.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkml@rtr.ca \
    --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.