From: Evgeniy Polyakov <johnpol@2ka.mipt.ru>
To: bert hubert <bert.hubert@netherlabs.nl>
Cc: Andi Kleen <andi@firstfloor.org>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: all syscalls initially taking 4usec on a P4? Re: nonblocking UDPv4 recvfrom() taking 4usec @ 3GHz?
Date: Wed, 21 Feb 2007 14:06:34 +0300 [thread overview]
Message-ID: <20070221110634.GA30394@2ka.mipt.ru> (raw)
In-Reply-To: <20070220171120.GD24930@2ka.mipt.ru>
Here is data for 50 bytes reading for essentially idle machine
(core duo 2.4 ghz):
delta for syscall: 3326961404-3326969261: 7857 cycles = 3.273750 us
delta for syscall: 3326975687-3326980979: 5292 cycles = 2.205000 us
delta for syscall: 3327199967-3327205583: 5616 cycles = 2.340000 us
delta for syscall: 3327208706-3327214817: 6111 cycles = 2.546250 us
delta for syscall: 3327442427-3327450446: 8019 cycles = 3.341250 us
delta for syscall: 3327453281-3327459104: 5823 cycles = 2.426250 us
delta for syscall: 3327462002-3327466844: 4842 cycles = 2.017500 us
delta for syscall: 3327726809-3327733451: 6642 cycles = 2.767500 us
delta for syscall: 3327736178-3327741947: 5769 cycles = 2.403750 us
delta for syscall: 3327968972-3327974264: 5292 cycles = 2.205000 us
delta for syscall: 3327977981-3327984506: 6525 cycles = 2.718750 us
delta for syscall: 3327987215-3327991958: 4743 cycles = 1.976250 us
delta for syscall: 3328245416-3328252058: 6642 cycles = 2.767500 us
delta for syscall: 3328258646-3328264172: 5526 cycles = 2.302500 us
and sometimes (frequently enough)
delta for syscall: 1937450129-1937469011: 18882 cycles = 7.867500 us
delta for syscall: 1956633332-1956654248: 20916 cycles = 8.715000 us
delta for syscall: 1995042065-1995061703: 19638 cycles = 8.182500 us
delta for syscall: 2014239488-2014257992: 18504 cycles = 7.710000 us
delta for syscall: 2016294674-2016316202: 21528 cycles = 8.970000 us
delta for syscall: 2054518259-2054537447: 19188 cycles = 7.995000 us
delta for syscall: 2071839668-2071857146: 17478 cycles = 7.282500 us
But there is even following sometimes:
delta for syscall: 3271734859-3271872037: 137178 cycles = 57.157501 us
Queue of the non-blocking socket is being kept full by another host
which sends udp with 40k chunks per socket write.
Reading /dev/zero in chunks of 50 bytes ends up with about 190
nanosecond on that machine.
--
Evgeniy Polyakov
next prev parent reply other threads:[~2007-02-21 11:07 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-19 23:14 nonblocking UDPv4 recvfrom() taking 4usec @ 3GHz? bert hubert
2007-02-19 23:56 ` Stephen Hemminger
2007-02-20 8:04 ` bert hubert
2007-02-20 10:50 ` Andi Kleen
2007-02-20 16:27 ` all syscalls initially taking 4usec on a P4? " bert hubert
2007-02-20 16:41 ` Evgeniy Polyakov
2007-02-20 17:02 ` bert hubert
2007-02-20 17:11 ` Evgeniy Polyakov
2007-02-20 17:18 ` Evgeniy Polyakov
2007-02-21 11:06 ` Evgeniy Polyakov [this message]
2007-02-21 11:34 ` Andi Kleen
2007-02-20 18:42 ` Josef Sipek
2007-02-20 18:48 ` Evgeniy Polyakov
2007-02-20 19:33 ` bert hubert
2007-02-20 19:40 ` Benjamin LaHaise
2007-02-20 20:45 ` bert hubert
2007-02-20 21:02 ` Stephen Hemminger
2007-02-20 22:02 ` Rick Jones
2007-02-20 22:17 ` bert hubert
2007-02-20 22:22 ` Arjan van de Ven
2007-02-21 16:25 ` Chuck Ebbert
2007-02-20 22:46 ` Ian McDonald
2007-02-25 10:41 ` Pavel Machek
2007-02-25 17:06 ` Evgeniy Polyakov
2007-02-20 16:57 ` Eric Dumazet
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=20070221110634.GA30394@2ka.mipt.ru \
--to=johnpol@2ka.mipt.ru \
--cc=andi@firstfloor.org \
--cc=bert.hubert@netherlabs.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).