From: Eric Dumazet <eric.dumazet@gmail.com>
To: Jesper Dangaard Brouer <jdb@comx.dk>
Cc: Linux Kernel Network Hackers <netdev@vger.kernel.org>,
Robert Olsson <robert@herjulf.net>
Subject: Re: Strange CPU load when flushing route cache (kernel 2.6.31.6)
Date: Mon, 23 Nov 2009 11:29:14 +0100 [thread overview]
Message-ID: <4B0A63FA.5000804@gmail.com> (raw)
In-Reply-To: <1258970332.29747.262.camel@jdb-workstation>
Jesper Dangaard Brouer a écrit :
> Hi Eric and netdev,
>
> I have observed a strange route cache behaviour when I upgraded some
> of my production Linux routers (1Gbit/s tg3) to kernel 2.6.31.6 (from
> kernel 2.6.25.7).
>
> Every time the route cache is flushed I get a CPU spike (in softirq)
> with a tail. I have attached some graphs that illustrate the issue
> (hope vger.kernel.org will allow these attachments...)
>
>
> I have done some tuning of the route cache:
>
> # From /etc/sysctl.conf
> #
> # Adjusting the route cache flush interval
> net/ipv4/route/secret_interval = 1200
>
> # Limiting the route cache size
> # ip_dst_cache slab objects is 256 bytes.
> # 2000000 * 256 bytes = 512 MB
> net/ipv4/route/max_size = 2000000
>
> Boot parameters: "rhash_entries=262143 vmalloc=256M"
>
> The rhash_entries is for the route cache hash size. The vmalloc is
> needed because I have _very_ large iptables rulesets (and is running
> on a 32-bit kernel, due to old hardware).
>
> Any thoughs on how to avoid these CPU spikes?
> Or where the issue occurs in the code?
>
Sure, after a flush, we have to rebuild the cache, so extra work is expected.
(We receive a packet, notice the cached entry is obsolete, free it, allocate a new one
and inert it into cache)
If you dont want these spikes, just dont flush cache :)
Do you run a 2G/2G User/Kernel split kernel ?
next prev parent reply other threads:[~2009-11-23 10:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-23 9:58 Strange CPU load when flushing route cache (kernel 2.6.31.6) Jesper Dangaard Brouer
2009-11-23 10:29 ` Eric Dumazet [this message]
2009-11-23 12:28 ` Jesper Dangaard Brouer
2009-11-23 13:25 ` Eric Dumazet
2009-11-23 13:48 ` Jesper Dangaard Brouer
2009-11-23 14:03 ` Eric Dumazet
2009-11-26 10:51 ` Jesper Dangaard Brouer
2009-11-26 11:05 ` Eric Dumazet
2009-11-23 15:07 ` robert
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=4B0A63FA.5000804@gmail.com \
--to=eric.dumazet@gmail.com \
--cc=jdb@comx.dk \
--cc=netdev@vger.kernel.org \
--cc=robert@herjulf.net \
/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).