From: "Peter Wächtler" <pwaechtler@loewe-komp.de>
To: "Ahmed, Zameer" <Zameer.Ahmed@gs.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Turning off nagle algorithm in 2.2.x and 2.4.x kernels?
Date: Tue, 18 Dec 2001 10:47:22 +0100 [thread overview]
Message-ID: <3C1F10AA.A2D5367@loewe-komp.de> (raw)
In-Reply-To: <FBC7494738B7D411BD7F00902798761908BFF190@gsny49e.ny.fw.gs.com>
"Ahmed, Zameer" schrieb:
>
> Hi,
> Is there a way to turn off nagle compression in the kernel for 2.2.x
> and 2.4.x kernels? For the same custom app used under Solaris and Linux.
> Turning off nagle algorithm boosted perf on Solaris, I tried commenting out
>
> #bool 'IP: Disable NAGLE algorithm (normally enabled)' CONFIG_TCP_NAGLE_OF
>
> from the net/ipv4/Config.in 2.2.19 kernel and still the degradation in
> network performance for packts in midsize persists
> I tried the 2.4.16 kernel. This gave me very slight improvement, but not
> quite what is expected.
>
there is a setsockopt() - apply it to the fd returned from accept()
man 7 tcp
SOCKET OPTIONS
To set or get a TCP socket option, call getsockopt(2) to
read or setsockopt(2) to write the option with the socket
family argument set to SOL_TCP. In addition, most SOL_IP
socket options are valid on TCP sockets. For more informa
tion see ip(7).
TCP_NODELAY
Turn the Nagle algorithm off. This means that pack
ets are always sent as soon as possible and no
unnecessary delays are introduced, at the cost of
more packets in the network. Expects an integer
boolean flag.
next prev parent reply other threads:[~2001-12-18 9:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-17 21:03 Turning off nagle algorithm in 2.2.x and 2.4.x kernels? Ahmed, Zameer
2001-12-17 22:12 ` Russell King
2001-12-18 4:27 ` Andi Kleen
2001-12-18 9:47 ` Peter Wächtler [this message]
2001-12-18 14:58 ` Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2001-12-18 17:05 Ahmed, Zameer
2001-12-18 17:59 ` Oliver Xymoron
2001-12-18 19:10 ` Alan Cox
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=3C1F10AA.A2D5367@loewe-komp.de \
--to=pwaechtler@loewe-komp.de \
--cc=Zameer.Ahmed@gs.com \
--cc=linux-kernel@vger.kernel.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