public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Baruch Even <baruch@ev-en.org>
To: Paul Dickson <paul@permanentmail.com>
Cc: dickson@permanentmail.com, linux-os@analogic.com,
	linux-kernel@vger.kernel.org
Subject: Re: Network speed Linux-2.6.10
Date: Wed, 02 Mar 2005 09:37:56 +0000	[thread overview]
Message-ID: <42258974.4080104@ev-en.org> (raw)
In-Reply-To: <20050301202400.36259d94.paul@permanentmail.com>

Paul Dickson wrote:
> On Wed, 02 Mar 2005 01:02:50 +0000, Baruch Even wrote:
> 
>>>Might this be related to the broken BicTCP implementations in the 2.6.6+
>>>kernels?  A fix was added around 2.6.11-rc3 or 4.
>>
>>Unlikely, the problem with BIC would have shown itself only at high 
>>speeds over long latency links, not over a lan connection.
> 
> I only mentioned the possibility because I saw the same profile given by
> the PDF (the link was mentioned in the patch) while downloading gnoppix
> via my cable modem.  The oscillations of speed varied from 40K to 500+K.
> The average ended up around 270K.  (I was using wget for the download).

If it is indeed BIC than we have a bug where it doesn't shut itself off 
for low latencies. Since we don't test this case extensively here (we 
work to improve high-speed and just make sure we don't ruin slower 
speeds) I can't say it's impossible, try turning BIC off and see if it 
helps.

Due to the scenario that the OP gave it is more likely something to do 
with auto-detection somewhere along the way or a driver bug. It is also 
possible that I'm mistaken and it is BIC, never hurts to check.

Baruch

      reply	other threads:[~2005-03-02  9:38 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-01 19:29 Network speed Linux-2.6.10 linux-os
2005-03-01 20:20 ` Ben Greear
2005-03-01 20:24   ` Lee Revell
2005-03-01 20:27     ` linux-os
2005-03-01 20:30     ` Miquel van Smoorenburg
2005-03-01 20:36       ` Lee Revell
2005-03-01 20:30     ` Ben Greear
2005-03-01 20:35       ` Lee Revell
2005-03-02 16:16       ` venom
2005-03-02 16:14     ` venom
2005-03-02 17:40     ` Horst von Brand
2005-03-02 17:48       ` linux-os
2005-03-01 20:26   ` linux-os
2005-03-01 20:34     ` Ben Greear
2005-03-02  0:51 ` Paul Dickson
2005-03-02  1:02   ` Baruch Even
2005-03-02  3:24     ` Paul Dickson
2005-03-02  9:37       ` Baruch Even [this message]

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=42258974.4080104@ev-en.org \
    --to=baruch@ev-en.org \
    --cc=dickson@permanentmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-os@analogic.com \
    --cc=paul@permanentmail.com \
    /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