How would one disable Nagle’s algorithm in Linux? [closed]

by

This flag (TCP_NODELAY) is an option that can be enabled on a per-socket basis and is applied when you create a TCP socket. This is done for a purpose: Nagle’s algorithm is generally useful and helps handle network congestion. I doubt you want to disable it system-wide since your system will probably suffer from this deactivation.

To disable it for a given socket, you can apply the option TCP_NODELAY as explained here and here in C:

int flag = 1;
int result = setsockopt(sock,            /* socket affected */
                        IPPROTO_TCP,     /* set option at TCP level */
                        TCP_NODELAY,     /* name of option */
                        (char *) &flag,  /* the cast is historical cruft */
                        sizeof(int));    /* length of option value */
 if (result < 0)
    ... handle the error ...

You may have to adapt to your programming language, but basically it sets the TCP_NODELAY flag option to the socket sock, effectively disabling Nagle’s algorithm. This is valid on any OS with sockets supporting the TCP standard.

If you still want to disable Nagle’s algorithm system-wide, two options are available. First, you could recompile your kernel using the according flag (see your distribution manual for this). The second option is to create a software that sets the TCP_NODELAY flag on every existing connection, similar to this code. The latter option should be executed each time a new TCP connection is created on the system.

Something a bit cleaner would be to activate the low latency mode of TCP:

echo 1 > /proc/sys/net/ipv4/tcp_low_latency

update: tcp_low_latency was removed in kernel v4.14 and above.

This will give a hint to the TCP stack as to which decisions to make in order to lower the latency (Which I guess is what you are trying to achieve by disabling Nagle’s algorithm). By default, it is set to optimize bandwidth ( “0” will be read from /proc/sys/net/ipv4/tcp_low_latency ).

More Related Contents:

  1. grep lines that contain 1 character followed by another character
  2. 32-bit absolute addresses no longer allowed in x86-64 Linux?
  3. How to convert DOS/Windows newline (CRLF) to Unix newline (LF) in a Bash script
  4. What’s the best way to send a signal to all members of a process group?
  5. How to prevent a background process from being stopped after closing SSH client in Linux
  6. What is double dot(..) and single dot(.) in Linux?
  7. How to print a number in assembly NASM?
  8. Exploring Docker container’s file system
  9. What’s the difference between nohup and ampersand
  10. Quickly create a large file on a Linux system
  11. Redirect STDERR / STDOUT of a process AFTER it’s been started, using command line?
  12. Linux static linking is dead?
  13. Can I programmatically “burn in” ANSI control codes to a file using unix utils?
  14. Using the passwd command from within a shell script
  15. Run bash script as daemon
  16. In Linux, how to tell how much memory processes are using?
  17. Number of executed Instructions different for Hello World program Nasm Assembly and C
  18. Bash Script – iterating over output of find
  19. How to print third column to last column?
  20. Git and hard links
  21. Running a self-contained ASP.NET Core application on Ubuntu
  22. How can I remove the BOM from a UTF-8 file? [duplicate]
  23. What is the difference between double-ampersand (&&) and semicolon (;) in Linux Bash?
  24. ssh: Could not resolve hostname [hostname]: nodename nor servname provided, or not known [closed]
  25. How do I script a “yes” response for installing programs?
  26. Print date for the monday of the current week (in bash)
  27. How do you filter out all unique lines in a file?
  28. Setting creation or change timestamps
  29. Why doesn’t “sort file1 > file1” work?
  30. How to set RPATH and RUNPATH with GCC/LD?

Leave a Comment