From: Denys Fedoryshchenko <denys@visp.net.lb>
To: Evgeniy Polyakov <johnpol@2ka.mipt.ru>
Cc: Eric Dumazet <dada1@cosmosbay.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: loaded router, excessive getnstimeofday in oprofile
Date: Wed, 27 Aug 2008 15:09:17 +0300 [thread overview]
Message-ID: <200808271509.18529.denys@visp.net.lb> (raw)
In-Reply-To: <20080826205158.GA15266@2ka.mipt.ru>
[-- Attachment #1: Type: text/plain, Size: 1344 bytes --]
On Tuesday 26 August 2008, Evgeniy Polyakov wrote:
> On Tue, Aug 26, 2008 at 10:44:56PM +0200, Eric Dumazet (dada1@cosmosbay.com)
wrote:
> > >Do you have any packet sockets in this system? Like running dhcp daemon?
No, nothing at all.
> >
> > Another way to see this problem can be to start a sniffer on the machine,
> > even with a restrictive pcap filter, to check if performance change or
> > not. (It should decrease)
Yes, when i run tcpdump even without promisc at peak time, machine will be
almost dead. Transit traffic will be 100ms+. I know that it is timestamping
packets. Same almost for any libpcap app.
>
> Or just check /proc/net/packet iirc.
> Anyway, having at least one packet socket ends up with timestamping of
> each packet, so you will get fair load of getnstimeofday() in that case.
There is very short list of tasks. Attached.
/proc/net/packet clean, nothing there.
>
> > For example, I believe that running "ping" could have the same effect
> > (increasing netstamp_needed variable : every incoming packet has to be
> > timestamped)
Even answering icmp timestamp request will take resources.
> >
> > So beware of pings, traceroute and other networking tools...
When i am measuring performance - they are all off.
>
> Yup, this innocent toys can end up with this such behaviour on modern
> highly loaded machines.
[-- Attachment #2: tasks.txt --]
[-- Type: text/plain, Size: 1169 bytes --]
tcp 0 0 127.0.0.1:2600 0.0.0.0:* LISTEN 3167/zebra
tcp 0 0 0.0.0.0:2601 0.0.0.0:* LISTEN 3167/zebra
tcp 0 0 0.0.0.0:2602 0.0.0.0:* LISTEN 3174/ripd
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 3549/sshd
tcp 0 0 194.146.153.17:22 194.146.154.161:37549 ESTABLISHED11593/sshd
tcp 0 0 194.146.153.17:22 192.168.0.92:45891 ESTABLISHED11803/sshd
tcp 0 0 127.0.0.1:42537 127.0.0.1:2600 ESTABLISHED3174/ripd
tcp 0 0 194.146.153.17:22 194.146.153.18:51810 ESTABLISHED11799/sshd
tcp 0 0 127.0.0.1:2600 127.0.0.1:42537 ESTABLISHED3167/zebra
udp 0 0 0.0.0.0:520 0.0.0.0:* 3174/ripd
udp 0 0 0.0.0.0:161 0.0.0.0:* 3194/snmpd
udp 0 0 0.0.0.0:67 0.0.0.0:* 3207/udhcpd
udp 111360 0 0.0.0.0:49619 0.0.0.0:* 2449/syslogd
next prev parent reply other threads:[~2008-08-27 12:10 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-22 1:57 loaded router, excessive getnstimeofday in oprofile Denys Fedoryshchenko
2008-08-22 2:23 ` Denys Fedoryshchenko
2008-08-26 9:51 ` Jarek Poplawski
2008-08-26 10:29 ` Denys Fedoryshchenko
2008-08-26 10:47 ` Jarek Poplawski
2008-08-26 10:49 ` Denys Fedoryshchenko
2008-08-26 11:07 ` Jarek Poplawski
2008-08-26 11:15 ` Jarek Poplawski
2008-08-26 11:16 ` Denys Fedoryshchenko
2008-08-26 11:32 ` Jarek Poplawski
2008-08-26 11:32 ` Denys Fedoryshchenko
2008-08-26 20:14 ` Evgeniy Polyakov
2008-08-26 20:44 ` Eric Dumazet
2008-08-26 20:51 ` Evgeniy Polyakov
2008-08-27 12:09 ` Denys Fedoryshchenko [this message]
2008-08-27 12:36 ` Evgeniy Polyakov
2008-08-27 14:00 ` Denys Fedoryshchenko
2008-08-27 14:23 ` Evgeniy Polyakov
2008-08-27 12:54 ` Andi Kleen
2008-08-27 16:07 ` Rick Jones
2008-08-27 16:27 ` Andi Kleen
2008-08-27 16:49 ` Rick Jones
2008-08-27 16:56 ` Andi Kleen
2008-08-27 16:57 ` Rick Jones
2008-08-27 17:27 ` Eric Dumazet
2008-08-27 18:32 ` loaded router, excessive getnstimeofday in oprofile\ Andi Kleen
2008-08-27 22:23 ` David Miller
2008-08-27 22:38 ` Andi Kleen
2008-08-27 22:18 ` loaded router, excessive getnstimeofday in oprofile David Miller
2008-08-27 22:39 ` Andi Kleen
2008-08-28 0:45 ` Nick Piggin
2008-08-28 0:48 ` David Miller
2008-08-28 1:07 ` Nick Piggin
2008-08-27 16:17 ` Stephen Hemminger
2008-08-27 17:14 ` Jarek Poplawski
2008-08-27 21:34 ` David Miller
2008-08-28 2:39 ` Jason Uhlenkott
2008-08-28 3:10 ` David Miller
2008-08-28 6:28 ` Joe Malicki
2008-08-28 7:22 ` Andi Kleen
2008-08-28 15:02 ` Denys Fedoryshchenko
2008-08-28 19:01 ` Ilpo Järvinen
2008-08-28 19:31 ` David Miller
2008-08-28 16:48 ` Denys Fedoryshchenko
2008-08-28 16:56 ` Andi Kleen
2008-08-28 18:57 ` Eric Dumazet
2008-08-28 19:25 ` Denys Fedoryshchenko
2008-08-28 19:37 ` Eric Dumazet
2008-08-28 19:55 ` Denys Fedoryshchenko
2008-08-29 15:43 ` Stephen Hemminger
2008-08-28 19:36 ` David Miller
2008-08-28 19:59 ` Denys Fedoryshchenko
2008-08-29 15:21 ` Joe Malicki
2008-08-29 15:30 ` Andi Kleen
2008-08-29 15:43 ` Joe Malicki
2008-08-29 20:43 ` Evgeniy Polyakov
2008-08-28 18:00 ` Rick Jones
2008-08-28 19:42 ` David Miller
2008-08-28 20:29 ` Rick Jones
2008-08-28 20:32 ` David Miller
2008-08-28 20:45 ` Rick Jones
2008-08-28 20:47 ` David Miller
2008-09-01 2:39 ` Valdis.Kletnieks
2008-09-01 3:51 ` David Miller
2008-09-01 4:08 ` Valdis.Kletnieks
2008-09-01 4:10 ` David Miller
2008-09-02 17:04 ` Rick Jones
2008-08-28 3:35 ` Stephen Hemminger
2008-08-28 8:49 ` Denys Fedoryshchenko
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=200808271509.18529.denys@visp.net.lb \
--to=denys@visp.net.lb \
--cc=dada1@cosmosbay.com \
--cc=johnpol@2ka.mipt.ru \
--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).