From: Robert Olsson <robert@robur.slu.se>
To: andrei.popa@i-neo.ro
Cc: NetDEV list <netdev@vger.kernel.org>, robert@robur.slu.se
Subject: [oops] with FIB_TRIE
Date: Tue, 12 May 2009 17:15:38 +0200 [thread overview]
Message-ID: <18953.37530.49022.415@robur.slu.se> (raw)
In-Reply-To: <1242041043.4619.56.camel@ierdnac>
Andrei Popa writes:
> I've used an vanilla 2.6.28.7 kernel without any additional patches with
> the following .config and when I do in quagga a "clear ip bgp * soft"
> when I have three full BGP sessions the kernel it oopses.
>
> With FIB lookup algorithm FIB_TRIE it oopeses. With FIB_HASH it doesn't.
>
> Pictures with the oops:
> http://89.33.136.9/oops/
> The config file:
> CONFIG_PREEMPT=y
Hello,
Getting somewhat worried as we use this for infrastructure since many years.
I've set up test and is trying to reproduce it.
I'm running forwarding ~9.4 Gigabit/s @ 1.2 pkts sec and fib_lookups 40-200.000
lookups per sec. Routing table has 280.000 entries this is loaded/unloaded
via ip route with -batch to give load for insert/delete.
A script is continuesly adding/removing the routing table under this load.
The time to install the full table is ~10 sec and same time to remove
(without netfilter ~5 sec) And this during this constant traffic load.
The scripts and routing tables:
ftp://robur.slu.se/pub/Linux/net-development/trie-test/
Drivers are niu, ixgbe Netfilter modules loaded but no filters. Kernel
2.6.29-r2.
No problems seen for 3 hours but I'll let this run overnight
One difference to your config I see is PREEMPT. We use use
CONFIG_PREEMPT_NONE=y with the router/servers.
Cheers
--ro
next prev parent reply other threads:[~2009-05-12 15:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-11 11:24 [oops] with FIB_TRIE Andrei Popa
2009-05-12 15:15 ` Robert Olsson [this message]
2009-05-14 11:54 ` Andrei Popa
2009-05-14 20:00 ` Stephen Hemminger
2009-05-14 21:55 ` Robert Olsson
2009-05-16 21:24 ` Paul E. McKenney
2009-05-17 13:44 ` Robert Olsson
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=18953.37530.49022.415@robur.slu.se \
--to=robert@robur.slu.se \
--cc=andrei.popa@i-neo.ro \
--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).