The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Joris Neujens <joris@discosmash.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Possible network issue in 2.6.8.1
Date: Tue, 07 Sep 2004 14:35:56 +0100	[thread overview]
Message-ID: <1094564155.9152.13.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.58.0409071544570.6867@asus.discosmash.com>

On Maw, 2004-09-07 at 14:55, Joris Neujens wrote:
> We have ruled out the following:
> Network source is slow (we were testing with the same FTP server all the
> time, from which we normally download at 10MB/sec)
> We tested with 3 different systems and network cards, and they all have
> the same problem, and only with kernel 2.6.8
> 
> any thoughts?

See the list archive, or the lwn article on broken routers mangling TCP
window size negotiation. The lwn article has a nice discussion as well
as workarounds if you need them.


  reply	other threads:[~2004-09-07 16:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-07 13:55 Possible network issue in 2.6.8.1 Joris Neujens
2004-09-07 13:35 ` Alan Cox [this message]
2004-09-07 14:29 ` Paolo Ornati
2004-09-07 23:09 ` Lee Revell

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=1094564155.9152.13.camel@localhost.localdomain \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=joris@discosmash.com \
    --cc=linux-kernel@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