public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Florian Boelstler <kernel@boelstler.net>
To: linux-kernel@vger.kernel.org
Cc: netdev@vger.kernel.org
Subject: Re: Strange delays / what usually happens every 10 min?
Date: Tue, 13 Nov 2007 18:54:12 +0100	[thread overview]
Message-ID: <fhcocb$jv0$1@ger.gmane.org> (raw)
In-Reply-To: <4739CF81.8050704@cosmosbay.com>

Hi Eric,

Eric Dumazet wrote:
> Instead of using less RAM, you could just boot with rhash_entries=1024 
> to lower the size of this table.

I just tried that and it seems to reduce the scan time. This is the 
result for the first 40 minutes of runtime:

root@mpc0:/# /tmp/wait.rt
looping 1 milli seconds nanosleep ...
17:10:11/425384 #1 MAX 1996/83117/-268599896 us/tick/usec (at 2107848557)
17:10:11/427385 #2 MAX 2001/83327/2001 us/tick/usec (at 2107931884)
17:10:11/433534 #5 MAX 2149/89477/2150 us/tick/usec (at 2108187839)
17:27:02/5897 #505291 MAX 2512/104576/2513 us/tick/usec (at 1223589469)

The first ~10ms delay usually occurred after ~15 minutes. So one could 
argue that the reported HIGH-value at 17:27:02 (GMT) is the first flush 
of IP route cache. And all later flushes weren't longer than 2,5ms.

Thanks to all of you, especially Eric. Now it seems I got an instrument 
to lower system response time.

Cheers,

   Florian

PS: Unfortunately I had to remove some CC:-entries since the local 
firewall seems to not allow anything but NNTP (for gmane) and HTTP.


      reply	other threads:[~2007-11-13 17:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-13 14:24 Strange delays / what usually happens every 10 min? Florian Boelstler
2007-11-13 14:41 ` Peter Zijlstra
2007-11-13 16:02 ` Dmitry Adamushko
2007-11-13 16:08 ` Chris Snook
2007-11-13 16:50   ` Clemens Koller
2007-11-13 17:58     ` Florian Boelstler
2007-11-13 16:23 ` Eric Dumazet
2007-11-13 17:54   ` Florian Boelstler [this message]

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='fhcocb$jv0$1@ger.gmane.org' \
    --to=kernel@boelstler.net \
    --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