Re: What happened to CONFIG_TCP_NAGLE_OFF?

["John Stoffel" <john@stoffel.org>]

>>>>> "Matt" == Matt Garman <matthew.garman@gmail.com> writes:

Matt> On 11/29/06, Phillip Susi <psusi@cfl.rr.com> wrote:
>> > 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.

Matt> I don't want to change the API at all.  I'm using a
Matt> closed-source, 3rd party library.  Using strace, I can see that
Matt> the library does *not* do a setsockopt(...TCP_NODELAY...) on
Matt> opened sockets.  Since I can't change the library, I would like
Matt> to patch and/or configure my kernel so that all TCP/IP sockets
Matt> default to TCP_NODELAY.

Can't you use the LD_PRELOAD trick to force your own custom library to
override the closed library, so that you can change the socket options
to be how you want them?

Wouldn't that be easier, and be less likely to screw up the whole
system?  

You could override the socket() call, so that you just pass through
all the parameters your library sets, and then you just put in your
own setsockopt() call on the socket, and return it as normal to the
library?  Hacky, but should do the trick if you're careful.

John