From: htmldeveloper@gmail.com (Peter Teoh)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Disabling nagle algorithm
Date: Mon, 30 May 2011 15:39:52 +0800 [thread overview]
Message-ID: <BANLkTimvRaQy0k702DWO-DHB9X5GWNn+rA@mail.gmail.com> (raw)
In-Reply-To: <BANLkTimK0A_=LH93Ei_-MJ-ygBR3m=HOmg@mail.gmail.com>
On Mon, May 30, 2011 at 12:47 PM, C K Kashyap <ckkashyap@gmail.com> wrote:
>
>
> On Mon, May 30, 2011 at 9:53 AM, Anupam Kapoor <anupam.kapoor@gmail.com>
> wrote:
>>
>> is tcp_nodelay not an option ?
>>
>
> Is this a socket option or is there a system wide setting for tcp_nodelay?
Yes, TCP_NODELAY is a socket option:
Going back to the kernel source:
include/linux/tcp.h:
#define TCP_NODELAY 1 /* Turn off Nagle's algorithm. */
and this:
u8 nonagle : 4,/* Disable Nagle algorithm? */
and looking into the kernel source code:
./fs/ocfs2/cluster/tcp.c:
ret = sock->ops->setsockopt(sock, SOL_TCP, TCP_NODELAY,
./net/rds/tcp.c:
sock->ops->setsockopt(sock, SOL_TCP, TCP_NODELAY, (char __user *)&val,
the above are just two of the examples of how to set TCP_NODELAY in the kernel.
At the userspace level:
http://www.linuxquestions.org/questions/other-*nix-55/how-do-i-disable-the-nagle-algorithm-in-enterprise-linux-3-kernel-ver-2-4-21-4-a-556170/
should be the correct way, except that the poster is attempting to do
it in a kernel that does not support it.
As documented in http://linux.die.net/man/7/tcp, the supported kernel
is 2.5.71 and onwards.
--
Regards,
Peter Teoh
next prev parent reply other threads:[~2011-05-30 7:39 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 [this message]
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
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=BANLkTimvRaQy0k702DWO-DHB9X5GWNn+rA@mail.gmail.com \
--to=htmldeveloper@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).