From: "Vincent Vanackere" <vincent.vanackere@gmail.com>
To: "Brice Figureau" <brice+lklm@daysofwonder.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.17: slow (as hell) tcp inbound transfers
Date: Mon, 19 Jun 2006 16:17:12 +0200 [thread overview]
Message-ID: <65258a580606190717t2cc5b28eg10fb4d64fe5ec1f3@mail.gmail.com> (raw)
In-Reply-To: <1150725598.4985.27.camel@localhost.localdomain>
On 6/19/06, Brice Figureau <brice+lklm@daysofwonder.com> wrote:
> Hi,
>
> First: please CC: me as I'm not subscribed to the list.
>
> Now to the problem: I just finished the installation of a brand new
> 2.6.17 on a Dell PowerEdge 2850 which was running 2.6.16.19 really fine,
> and I'm encountering a strange issue.
>
> 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
Vincent
next prev parent reply other threads:[~2006-06-19 14:17 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 [this message]
2006-06-19 14:59 ` Brice Figureau
2006-06-19 15:15 ` Con Kolivas
2006-06-19 15:52 ` Brice Figureau
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=65258a580606190717t2cc5b28eg10fb4d64fe5ec1f3@mail.gmail.com \
--to=vincent.vanackere@gmail.com \
--cc=brice+lklm@daysofwonder.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