From: Gregory Maxwell <greg@linuxpower.cx>
To: Corey Minyard <minyard@acm.org>
Cc: Zwane Mwaikambo <zwane@linux.realnet.co.sz>,
"Richard B. Johnson" <root@chaos.analogic.com>,
Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: TCP/IP Speed
Date: Wed, 30 Jan 2002 13:24:42 -0500 [thread overview]
Message-ID: <20020130132442.A12754@xi.linuxpower.cx> (raw)
In-Reply-To: <Pine.LNX.4.44.0201301831120.5518-100000@netfinity.realnet.co.sz> <3C583655.6060707@acm.org>
In-Reply-To: <3C583655.6060707@acm.org>; from minyard@acm.org on Wed, Jan 30, 2002 at 12:07:17PM -0600
On Wed, Jan 30, 2002 at 12:07:17PM -0600, Corey Minyard wrote:
> Zwane Mwaikambo wrote:
> >You didn't make that explicit in your previous email, and anyway what kind
> >of resolution can you expect from gettimeofday...
> >
> Depending on the processor, gettimeofday has very high resolution.
> If I remember correctly, the TCP stacks put in delays for small sends so
> they can pack multiple things together. I think there are ways to work
> around this via some type of flush, but memory fails me on exactly how.
Please! People, if you don't know exactly what you are talking about, at
least keep your replies off list.
The problem he's having is caused by nagle, I replied to him off list
because not knowing the API to disable a perfectly standard TCP behavior is
not related to kernel development.
I get enough traffic from this list without having a dozen blind people
trying to lead the blind.
It's great that you are trying to be helpful, but please do it off list,
unless it's actual pertinent to kernel development.
[For future archive searchers: The solution is to set the TCP_NODELAY socket
option]
next prev parent reply other threads:[~2002-01-30 18:24 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 [this message]
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
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=20020130132442.A12754@xi.linuxpower.cx \
--to=greg@linuxpower.cx \
--cc=linux-kernel@vger.kernel.org \
--cc=minyard@acm.org \
--cc=root@chaos.analogic.com \
--cc=zwane@linux.realnet.co.sz \
/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