From: "CIT/Paul" <xerox@foonet.net>
To: <linux-kernel@vger.kernel.org>
Subject: Disabling route-cache?
Date: Sat, 5 Oct 2002 12:25:47 -0400 [thread overview]
Message-ID: <006601c26c8b$dd16d430$4a00000a@badass> (raw)
To: 'linux-kernel@vger.kernel.org'
Subject: Disabling route-cache?
We have some linux routers and wish to disable the route cache. Is there
a way to do that?
The route cache is using so much of the CPU that it is making routing
ineffective. We are routing high
PPS > 100,000 and with the route cache enabled it will not even do half
of that. We tested by creating
a single ip -> ip flow at 100,000 pps and the machine routed it just
fine, however when we create a 100,000 ip -> 100,000 ip test
the machine drops 80% of the packets due to creating and tearing down
massive entries in the route cache.
I wish for it to work like Cisco's CEF with only an adjacency cache and
not a route cache for every flow.
I don't know why it doesn't work this way in the first place. Only the
ip_conntrack should keep track of flows (on a side note
if we enable ip_conntrack the whole machine goes to pot, there's no way
it's going to do it with that module loaded).
Please if anyone has any ideas. Thanks
reply other threads:[~2002-10-05 16:20 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='006601c26c8b$dd16d430$4a00000a@badass' \
--to=xerox@foonet.net \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®