From: "David S. Miller" <davem@redhat.com>
To: root@chaos.analogic.com
Cc: landley@trommello.org, linux-kernel@vger.kernel.org
Subject: Re: TCP/IP Speed
Date: Wed, 30 Jan 2002 13:58:04 -0800 (PST) [thread overview]
Message-ID: <20020130.135804.08322556.davem@redhat.com> (raw)
In-Reply-To: <Pine.LNX.3.95.1020130163406.21490A-100000@chaos.analogic.com>
In-Reply-To: <20020130212344.ZLSQ25963.femail43.sdc1.sfba.home.com@there> <Pine.LNX.3.95.1020130163406.21490A-100000@chaos.analogic.com>
From: "Richard B. Johnson" <root@chaos.analogic.com>
Date: Wed, 30 Jan 2002 16:54:46 -0500 (EST)
No. I set all sockets, even the original listen() socket to
TCP_NODELAY.
How about setting it on the resulting socket, not just the
listen one? Ie. at both ends always set TCP_NODELAY to 1
on each new socket created.
Nagle (Ie. TCP_NODELAY) is the only thing which could explain
the behavior you are complaining about.
next prev parent reply other threads:[~2002-01-30 22:00 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-30 16:07 TCP/IP Speed Richard B. Johnson
2002-01-30 16:14 ` Zwane Mwaikambo
2002-01-30 16:35 ` Richard B. Johnson
2002-01-30 16:31 ` Zwane Mwaikambo
2002-01-30 16:47 ` Richard B. Johnson
2002-01-30 16:45 ` Zwane Mwaikambo
2002-01-31 14:00 ` Terje Eggestad
2002-01-31 15:26 ` Richard B. Johnson
2002-01-31 16:06 ` Terje Eggestad
2002-01-30 18:07 ` Corey Minyard
2002-01-30 18:20 ` Tobias Ringstrom
2002-01-30 18:24 ` Gregory Maxwell
2002-01-30 16:36 ` Zwane Mwaikambo
2002-01-30 21:24 ` Rob Landley
2002-01-30 21:54 ` Richard B. Johnson
2002-01-30 21:58 ` David S. Miller [this message]
2002-01-31 13:33 ` Gregory Maxwell
[not found] <fa.kdqjrkv.1d44lam@ifi.uio.no>
2002-01-30 18:18 ` Dan Maas
2002-01-30 18:34 ` Richard B. Johnson
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=20020130.135804.08322556.davem@redhat.com \
--to=davem@redhat.com \
--cc=landley@trommello.org \
--cc=linux-kernel@vger.kernel.org \
--cc=root@chaos.analogic.com \
/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