mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Sébastien Dugué" <sebastien.dugue@bull.net>
To: Mike Galbraith <efault@gmx.de>
Cc: Ingo Molnar <mingo@elte.hu>,
	linux-kernel@vger.kernel.org,
	Thomas Gleixner <tglx@linutronix.de>,
	John Stultz <johnstul@us.ibm.com>,
	Deepak Saxena <dsaxena@plexity.net>
Subject: Re: 2.6.17-rc6-rt1
Date: Fri, 09 Jun 2006 14:57:01 +0200	[thread overview]
Message-ID: <1149857821.3829.42.camel@frecb000686> (raw)
In-Reply-To: <1149855638.7413.8.camel@Homer.TheSimpsons.net>

On Fri, 2006-06-09 at 14:20 +0200, Mike Galbraith wrote:
> > 
> >   I'm starting to believe that it's network related. Pinging my box from
> > a remote host gives a ~.3 ms round trip whereas pinging localhost gives
> > ~500ms. Something real weird is going on here.
> 
> Wow.  I don't see anything near 500ms, but I am dropping packets, and
> recvmsg, when it isn't saying -EAGAIN, is indeed taking way too long.
> 
> 14:04:02.062550 sendmsg(3, {msg_name(16)={sa_family=AF_INET, sin_port=htons(0), sin_addr=inet_addr("127.0.0.1")}, msg_iov(1)=[{"\10\0$@\217\36\0\2\262c\211D\35\364\0\0\10\t\n\v\f\r\16"..., 64}], msg_controllen=0, msg_flags=0}, 0) = 64 <0.000048>
> 14:04:02.062731 setitimer(ITIMER_REAL, {it_interval={0, 0}, it_value={10, 0}}, NULL) = 0 <0.000016>
> 14:04:02.062826 recvmsg(3, {msg_name(16)={sa_family=AF_INET, sin_port=htons(19889), sin_addr=inet_addr("127.0.0.1")}, msg_iov(1)=[{"E\0\0T\177]\0\0@\1\375I\177\0\0\1\177\0\0\1\0\0,@\217\36"..., 192}], msg_controllen=20, {cmsg_len=20, cmsg_level=SOL_SOCKET, cmsg_type=0x1d /* SCM_??? */, ...}, msg_flags=0}, 0) = 84 <0.037660>
> 

  Even weirder:

$ping localhost
PING localhost.localdomain (127.0.0.1) 56(84) bytes of data.
64 bytes from localhost.localdomain (127.0.0.1): icmp_seq=1 ttl=64 time=0.157 ms
64 bytes from localhost.localdomain (127.0.0.1): icmp_seq=2 ttl=64 time=107 ms
64 bytes from localhost.localdomain (127.0.0.1): icmp_seq=3 ttl=64 time=94.7 ms
64 bytes from localhost.localdomain (127.0.0.1): icmp_seq=4 ttl=64 time=741 ms
64 bytes from localhost.localdomain (127.0.0.1): icmp_seq=5 ttl=64 time=179 ms
64 bytes from localhost.localdomain (127.0.0.1): icmp_seq=6 ttl=64 time=732 ms
64 bytes from localhost.localdomain (127.0.0.1): icmp_seq=7 ttl=64 time=728 ms
64 bytes from localhost.localdomain (127.0.0.1): icmp_seq=8 ttl=64 time=725 ms
64 bytes from localhost.localdomain (127.0.0.1): icmp_seq=9 ttl=64 time=178 ms
64 bytes from localhost.localdomain (127.0.0.1): icmp_seq=10 ttl=64 time=96.0 ms
64 bytes from localhost.localdomain (127.0.0.1): icmp_seq=11 ttl=64 time=342 ms
...

$strace -tt -T ping localhost
14:48:07.764888 sendmsg(3, {msg_name(16)={sa_family=AF_INET, sin_port=htons(0), 
sin_addr=inet_addr("127.0.0.1")}, msg_iov(1)=[{"\10\0:\221\341\v\0\3\7n\211DU\25
2\v\0\10\t\n\v\f\r\16\17"..., 64}], msg_controllen=0, msg_flags=0}, MSG_CONFIRM)
 = 64 <0.000078>
14:48:07.765930 recvmsg(3, {msg_name(16)={sa_family=AF_INET, sin_port=htons(0), 
sin_addr=inet_addr("127.0.0.1")}, msg_iov(1)=[{"E\0\0T\\\241\0\0@\1 \6\177\0\0\1
\177\0\0\1\0\0B\221\341"..., 192}], msg_controllen=20, {cmsg_len=20, cmsg_level=
SOL_SOCKET, cmsg_type=0x1d /* SCM_??? */, ...}, msg_flags=0}, 0) = 84 <0.000402>
14:48:07.767598 write(1, "64 bytes from localhost.localdom"..., 8064 bytes from 
localhost.localdomain (127.0.0.1): icmp_seq=3 ttl=64 time=1.86 ms
) = 80 <0.000307>

All the round trips under strace are in the 2ms range.

  How on earth can it be that stracing the ping gives better
performance???

  Sébastien.








  reply	other threads:[~2006-06-09 12:52 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-07 21:14 2.6.17-rc6-rt1 Ingo Molnar
2006-06-08  2:09 ` 2.6.17-rc6-rt1 Daniel Walker
2006-06-08  3:49 ` 2.6.17-rc6-rt1 Mark Knecht
2006-06-08 20:12   ` 2.6.17-rc6-rt1 Mark Knecht
2006-06-08  6:42 ` [PATCH -rt] Trivial compiler warning fix Jan Altenberg
2006-06-08  8:51 ` 2.6.17-rc6-rt1 Mike Galbraith
2006-06-08 19:52   ` 2.6.17-rc6-rt1 john stultz
2006-06-08 20:01     ` 2.6.17-rc6-rt1 Thomas Gleixner
2006-06-08 10:28 ` 2.6.17-rc6-rt1 Michal Piotrowski
2006-06-08 12:23   ` 2.6.17-rc6-rt1 Michal Piotrowski
2006-06-08 11:28 ` 2.6.17-rc6-rt1 Michal Piotrowski
2006-06-08 18:27 ` 2.6.17-rc6-rt1 Kevin Hilman
2006-06-08 19:03   ` 2.6.17-rc6-rt1 Thomas Gleixner
2006-06-08 23:57 ` 2.6.17-rc6-rt1 john stultz
2006-06-09  7:28   ` 2.6.17-rc6-rt1 Thomas Gleixner
2006-06-09  8:42 ` 2.6.17-rc6-rt1 Mike Galbraith
2006-06-09 10:12   ` 2.6.17-rc6-rt1 Sébastien Dugué
2006-06-09 11:35     ` 2.6.17-rc6-rt1 Mike Galbraith
2006-06-09 11:44       ` 2.6.17-rc6-rt1 Sébastien Dugué
2006-06-09 12:20         ` 2.6.17-rc6-rt1 Mike Galbraith
2006-06-09 12:57           ` Sébastien Dugué [this message]
2006-06-09 13:11             ` 2.6.17-rc6-rt1 Thomas Gleixner
2006-06-09 13:42               ` 2.6.17-rc6-rt1 Mike Galbraith
2006-06-09 14:31                 ` 2.6.17-rc6-rt1 Thomas Gleixner
2006-06-09 15:55                 ` 2.6.17-rc6-rt1 Daniel Walker
2006-06-09 18:41                   ` 2.6.17-rc6-rt1 Mike Galbraith
2006-06-09 19:09                     ` 2.6.17-rc6-rt1 Thomas Gleixner

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=1149857821.3829.42.camel@frecb000686 \
    --to=sebastien.dugue@bull.net \
    --cc=dsaxena@plexity.net \
    --cc=efault@gmx.de \
    --cc=johnstul@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.de \
    /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

all inboxes | Powered by JetHome®