From: Carlo Wood <carlo@alinoe.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [ircu-development] Slow on high-MTU (local host) connections?
Date: Wed, 7 Nov 2001 04:35:54 +0100 [thread overview]
Message-ID: <20011107043554.B15045@alinoe.com> (raw)
In-Reply-To: <87snbstzfz.fsf@sanosuke.troilus.org> <20011107041140.A12198@alinoe.com> <20011107042153.A13705@alinoe.com>
In-Reply-To: <20011107042153.A13705@alinoe.com>; from carlo@alinoe.com on Wed, Nov 07, 2001 at 04:21:53AM +0100
The examples in the previous mail are from the case with MTU is 8000
(and were to only two occurances of a EAGAIN for read() actually).
Allow me show the statistics for both MTU's:
MTU 16436:
~>grep -B1 '\[srvx2\] select.*<0\.[1-9]' mtu16436 | grep '\[srvx2\] read' | wc --lines
323
~>grep -B1 '\[srvx2\] select.*<0\.[1-9]' mtu16436 | grep '\[srvx2\] read.*EAGAIN' | wc --lines
323
Conclusion: ALL calls to select() that took longer than 0.1 second
were following a call to read() that failed with EAGAIN. In total 323 times.
MTU 8000:
~>grep -B1 '\[srvx2\] select.*<0\.[1-9]' mtu8000 | grep '\[srvx2\] read' | wc --lines
2
~>grep -B1 '\[srvx2\] select.*<0\.[1-9]' mtu8000 | grep '\[srvx2\] read.*EAGAIN' | wc --lines
2
Idem, but only two occurences.
The total number of calls to select in both are respectively:
~>grep '\[srvx2\] select.*' mtu16436 | wc --lines
1221
~>grep '\[srvx2\] select.*' mtu8000 | wc --lines
658
--
Carlo Wood <carlo@alinoe.com>
(Also forwarded because first I used a wrong address)
next parent reply other threads:[~2001-11-07 3:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87snbstzfz.fsf@sanosuke.troilus.org>
[not found] ` <20011107041140.A12198@alinoe.com>
[not found] ` <20011107042153.A13705@alinoe.com>
2001-11-07 3:35 ` Carlo Wood [this message]
2001-11-07 3:34 [ircu-development] Slow on high-MTU (local host) connections? Carlo Wood
2001-11-07 3:52 ` David S. Miller
2001-11-07 15:23 ` Carlo Wood
2001-11-09 16:04 ` Entrope
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=20011107043554.B15045@alinoe.com \
--to=carlo@alinoe.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