netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hans de Goede <j.w.r.degoede@hhs.nl>
To: Eric Dumazet <dada1@cosmosbay.com>
Cc: Dave Jones <davej@redhat.com>, netdev@vger.kernel.org
Subject: Re: cat /proc/net/tcp takes 0.5 seconds on x86_64
Date: Wed, 27 Aug 2008 11:14:17 +0200	[thread overview]
Message-ID: <48B51AE9.5080709@hhs.nl> (raw)
In-Reply-To: <48B47543.8080701@cosmosbay.com>

Eric Dumazet wrote:
> 
> I dont know, you tell us 50x, but nowhere I saw your numbers on i386,
> nor the amount of memory of your test machine.
> 

My machine has 2 Gb of memory, but that is not really relevant as I'm not the 
reporter of the problem (but I can reproduce it) I'm only in the loop because I 
maintain the gkrellm package in Fedora which exhibits this problem. Also I gave 
you no i386 numbers on the same machine because I don't have an i386 install 
readily available on this machine.

Now you can spin this anyway you want, but lets cut to the chase, gkrellmd 
which is a system monitoring daemon reads /proc/net/tcp and /proc/net/tcp6 3 
times a second, with slightly older kernel this used to give a CPU load of
2-3% on x86_64 now it gives a load of 50-70% (on my test machine with a whole 8 
tcp connections open).

Now you can wing it any way you want, but this is a serious regression. I don't 
want to go to lkml and start shouting regression REGRESSION regression, but 
given the treating and enormous amount of help I've received sofar (and 
remember I'm only the messenger I didn't write nor use gkrellmd) I'm tending 
towards starting shouting regression on lkml, as atleast there this seems to 
get some attention.

Regards,

Hans

  reply	other threads:[~2008-08-27  9:03 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-459782-176318@bugzilla.redhat.com>
     [not found] ` <200808261549.m7QFnVUN032543@bz-web1.app.phx.redhat.com>
2008-08-26 16:37   ` cat /proc/net/tcp takes 0.5 seconds on x86_64 Dave Jones
2008-08-26 18:32     ` Eric Dumazet
2008-08-26 19:01       ` Hans de Goede
2008-08-26 20:39         ` Eric Dumazet
2008-08-26 20:58           ` Hans de Goede
2008-08-26 21:27             ` Eric Dumazet
2008-08-27  9:14               ` Hans de Goede [this message]
2008-08-27  9:05                 ` David Miller
2008-08-27  9:45                   ` Hans de Goede
2008-08-27  9:39                     ` David Miller
2008-08-27  4:19         ` Herbert Xu
2008-08-27  9:07           ` Hans de Goede
2008-08-27 12:41     ` Andi Kleen
2008-08-27 21:29       ` Trent Piepho
2008-08-27 21:47         ` Andi Kleen
2008-08-27 22:54           ` Andi Kleen
2008-08-27 21:29       ` David Miller
2008-08-27 21:48         ` Stephen Hemminger
2008-08-27 22:09           ` David Miller
2008-08-28  6:20             ` Eric Dumazet
2008-08-28  6:51               ` David Miller
2008-08-28  7:13                 ` Eric Dumazet
2008-08-28  7:57                   ` David Miller
2008-08-28  9:52                     ` Eric Dumazet
2008-08-28  7:26               ` Andi Kleen
2008-08-27 22:34         ` Andi Kleen
2008-08-27 22:39           ` David Miller
2008-08-27 22:57             ` Andi Kleen
2008-08-27 23:07               ` David Miller
2008-08-27 23:09             ` Eric Dumazet
2008-08-27 23:15               ` David Miller
2008-08-27 23:35                 ` Andi Kleen
2008-08-27 23:43                 ` Eric Dumazet
2008-08-27 23:45                   ` David Miller
2008-08-28  0:40                     ` Eric Dumazet
2008-08-28  7:45                       ` Andi Kleen
2008-08-28  7:59                         ` David Miller
2008-08-28  8:12                           ` Hans de Goede
2008-08-28  8:04                             ` David Miller

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=48B51AE9.5080709@hhs.nl \
    --to=j.w.r.degoede@hhs.nl \
    --cc=dada1@cosmosbay.com \
    --cc=davej@redhat.com \
    --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).