kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: mulyadi.santosa@gmail.com (Mulyadi Santosa)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Disabling nagle algorithm
Date: Tue, 31 May 2011 09:54:41 +0700	[thread overview]
Message-ID: <BANLkTik1MPq4mQ8Xz316R5Uq7Z3dQvFTBA@mail.gmail.com> (raw)
In-Reply-To: <BANLkTin7HRAuiHUnsQuxrf3iKZrJx04ZcA@mail.gmail.com>

On Tue, May 31, 2011 at 09:41, Anupam Kapoor <anupam.kapoor@gmail.com> wrote:
> yup, that's what i also think. is it possible that nagle+delayed-ack
> is causing the perceived slow-down ?

could be, but have you tried to switch and use various congestion
control ? check /proc/sys/net/ipv4/tcp_congestion_control and here are
enabled ones from my distro stock kernel:
$ grep -i cong /boot/config-`uname -r`
CONFIG_TCP_CONG_ADVANCED=y
CONFIG_TCP_CONG_BIC=y
CONFIG_TCP_CONG_CUBIC=y
CONFIG_TCP_CONG_WESTWOOD=m
CONFIG_TCP_CONG_HTCP=m
CONFIG_TCP_CONG_HSTCP=m
CONFIG_TCP_CONG_HYBLA=m
CONFIG_TCP_CONG_VEGAS=m
CONFIG_TCP_CONG_SCALABLE=m
CONFIG_TCP_CONG_LP=m
CONFIG_TCP_CONG_VENO=m
CONFIG_TCP_CONG_YEAH=m
CONFIG_TCP_CONG_ILLINOIS=m
CONFIG_DEFAULT_TCP_CONG="cubic"

-- 
regards,

Mulyadi Santosa
Freelance Linux trainer and consultant

blog: the-hydra.blogspot.com
training: mulyaditraining.blogspot.com

  reply	other threads:[~2011-05-31  2:54 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-29 17:34 Disabling nagle algorithm C K Kashyap
2011-05-30  3:48 ` Anupam Kapoor
2011-05-30  3:51   ` C K Kashyap
2011-05-30  4:23     ` Anupam Kapoor
2011-05-30  4:47       ` C K Kashyap
2011-05-30  7:39         ` Peter Teoh
2011-05-30  8:07           ` C K Kashyap
2011-05-30  8:34             ` Peter Teoh
2011-05-30 13:48               ` C K Kashyap
2011-05-31  0:33                 ` Peter Teoh
2011-05-31  2:41                   ` Anupam Kapoor
2011-05-31  2:54                     ` Mulyadi Santosa [this message]
2011-06-01  5:31                     ` Anupam Kapoor

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=BANLkTik1MPq4mQ8Xz316R5Uq7Z3dQvFTBA@mail.gmail.com \
    --to=mulyadi.santosa@gmail.com \
    --cc=kernelnewbies@lists.kernelnewbies.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;
as well as URLs for NNTP newsgroup(s).