From: Phillip Susi <psusi@cfl.rr.com>
To: Matt Garman <matthew.garman@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: What happened to CONFIG_TCP_NAGLE_OFF?
Date: Wed, 29 Nov 2006 15:06:55 -0500 [thread overview]
Message-ID: <456DE85F.50806@cfl.rr.com> (raw)
In-Reply-To: <bdd6985b0611281405j3e731e3xc7973c0365428663@mail.gmail.com>
Matt Garman wrote:
> I would like to globally disable nagling on my (2.6.9) system. There
> are several references on the web to the CONFIG_TCP_NAGLE_OFF kernel
> config option. However, it appears as though this no longer exists.
>
> How might I achieve having TCP_NODELAY effectively set for all sockets
> (by default)? Is there a new/different kernel config option, a patch,
> a sysctl or proc setting? Or can I "fake" this behavior by, e.g.
> setting a send buffer sufficiently small?
This is a bad idea and breaks api compatibility. Nagle is very
important for sockets being used for things like telnet. Other
applications, like ftp, should already disable nagle themselves.
next prev parent reply other threads:[~2006-11-29 20:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-28 22:05 What happened to CONFIG_TCP_NAGLE_OFF? Matt Garman
2006-11-29 20:06 ` Phillip Susi [this message]
2006-11-30 17:21 ` Matt Garman
2006-11-30 19:12 ` John Stoffel
2006-11-30 19:45 ` Phillip Susi
2006-12-01 0:00 ` Alan
2006-12-01 20:42 ` Phillip Susi
2006-12-02 3:29 ` Herbert Xu
2006-12-04 15:35 ` Phillip Susi
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=456DE85F.50806@cfl.rr.com \
--to=psusi@cfl.rr.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew.garman@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.