linux-kernel - Re: What happened to CONFIG_TCP_NAGLE

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <456DE85F.50806@cfl.rr.com>
Date:	Wed, 29 Nov 2006 15:06:55 -0500
From:	Phillip Susi <psusi@....rr.com>
To:	Matt Garman <matthew.garman@...il.com>
CC:	linux-kernel@...r.kernel.org
Subject: Re: What happened to CONFIG_TCP_NAGLE_OFF?

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.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/