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 14:25:21 +0100 [thread overview]
Message-ID: <4B0A8D41.6010608@gmail.com> (raw)
In-Reply-To: <1258979320.29747.270.camel@jdb-workstation>
Jesper Dangaard Brouer a écrit :
> On Mon, 2009-11-23 at 11:29 +0100, Eric Dumazet wrote:
>> Sure, after a flush, we have to rebuild the cache, so extra work is expected.
>
> But the old 2.6.25.7 do NOT show this behavior... That is the real
> issue...
Previous kernels were crashing, because flush was immediate and not deferred
as today.
During flush, we were dropping enormous amounts of packets.
Now, its possible to have setups with equilibrium and no packet loss,
because we smoothtly invalidate cache entries.
> I did the cache flushing due to some historical issues, that I think you
> did a fix for... Guess I can drop the flushing and see if the garbage
> collection can keep up...
Yes it can. Unless your route cache settings are not optimal.
>
>> Do you run a 2G/2G User/Kernel split kernel ?
>
> Not sure, how do I check?
grep LowTotal /proc/meminfo
or
dmesg | grep LOWMEM
913MB LOWMEM available. (standard 3G/1G User/Kernel split)
next prev parent reply other threads:[~2009-11-23 13:25 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
2009-11-23 12:28 ` Jesper Dangaard Brouer
2009-11-23 13:25 ` Eric Dumazet [this message]
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=4B0A8D41.6010608@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).