All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brice Figureau <brice+lklm@daysofwonder.com>
To: Con Kolivas <kernel@kolivas.org>
Cc: linux-kernel@vger.kernel.org,
	Vincent Vanackere <vincent.vanackere@gmail.com>
Subject: Re: 2.6.17: slow (as hell) tcp inbound transfers
Date: Mon, 19 Jun 2006 17:52:43 +0200	[thread overview]
Message-ID: <1150732363.4985.44.camel@localhost.localdomain> (raw)
In-Reply-To: <200606200115.02492.kernel@kolivas.org>

On Tue, 2006-06-20 at 01:15 +1000, Con Kolivas wrote:
> On Tuesday 20 June 2006 00:59, Brice Figureau wrote:
> > On Mon, 2006-06-19 at 16:17 +0200, Vincent Vanackere wrote:
> > > On 6/19/06, Brice Figureau <brice+lklm@daysofwonder.com> wrote:
> > > > It seems that TCP inbound transfers (using either curl, or scp) are
> > > > really slow except when issued on our gigabit LAN.
> > >
> > > Could you try the following to see if it cures your problem ?
> > >
> > > echo 0 > /proc/sys/net/ipv4/tcp_window_scaling
> >
> > Yes, that fixed it:
> > [snipped]
> > Did something has changed between 2.6.16 and 2.6.17 regarding TCP window
> > scaling ?
> >
> > I remember a discussion on lklm aroung 2.6.7 or so that finally ended as
> > a bug in a firewall that wasn't handling TCP window scaling gracefully.
> > That's certainly my case, I'll will have a look to that.
> 
> See:
> 
> http://kerneltrap.org/node/6723

Thanks for the pointer and sorry for the noise.
-- 
Brice Figureau


      reply	other threads:[~2006-06-19 15:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-19 13:59 2.6.17: slow (as hell) tcp inbound transfers Brice Figureau
2006-06-19 14:17 ` Vincent Vanackere
2006-06-19 14:59   ` Brice Figureau
2006-06-19 15:15     ` Con Kolivas
2006-06-19 15:52       ` Brice Figureau [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=1150732363.4985.44.camel@localhost.localdomain \
    --to=brice+lklm@daysofwonder.com \
    --cc=kernel@kolivas.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vincent.vanackere@gmail.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 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.