From: Corey Minyard <minyard@acm.org>
To: Zwane Mwaikambo <zwane@linux.realnet.co.sz>
Cc: "Richard B. Johnson" <root@chaos.analogic.com>,
Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: TCP/IP Speed
Date: Wed, 30 Jan 2002 12:07:17 -0600 [thread overview]
Message-ID: <3C583655.6060707@acm.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0201301831120.5518-100000@netfinity.realnet.co.sz>
Zwane Mwaikambo wrote:
>On Wed, 30 Jan 2002, Richard B. Johnson wrote:
>
>>But it's already connected.
>>
>>
>> host:
>> for (;;) {
>> gettimeofday(...);
>> write(s, buf, 64);
>> read(s, buf, sizeof(buffer));
>> gettimeofday(...);
>> /* delay is 1.0 ms */
>> }
>> server is IPPORT_ECHO
>>
>
>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.
-Corey
next prev parent reply other threads:[~2002-01-30 18:09 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 [this message]
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
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=3C583655.6060707@acm.org \
--to=minyard@acm.org \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.