From: "David S. Miller" <davem@redhat.com>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: niv@us.ibm.com, Paul.McKenney@us.ibm.com, netdev@oss.sgi.com
Subject: Re: [RFC] Use RCU for fib_rules
Date: Wed, 31 Mar 2004 13:11:07 -0800 [thread overview]
Message-ID: <20040331131107.151005a7.davem@redhat.com> (raw)
In-Reply-To: <20040331130541.4b1e8b0d@dell_ss3.pdx.osdl.net>
On Wed, 31 Mar 2004 13:05:41 -0800
Stephen Hemminger <shemminger@osdl.org> wrote:
> No, don't have enough rules or load in this area to cause an impact.
> But also, I don't have the test environment to really stress this
> (ie 1000's of rules).
You really don't need 1000's of rules. Every time the routing cache
misses, it's going to dive into this code, so on SMP that would show up.
You could use stream.c (http://www.securiteam.com/unixfocus/5YP0I000DG.html)
as the DoS workload in order to thrash the routing cache and force the
rule codepath.
next prev parent reply other threads:[~2004-03-31 21:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-31 19:28 [RFC] Use RCU for fib_rules Stephen Hemminger
2004-03-31 20:20 ` Nivedita Singhvi
2004-03-31 21:05 ` Stephen Hemminger
2004-03-31 21:11 ` David S. Miller [this message]
2004-03-31 23:40 ` Paul McKenney
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=20040331131107.151005a7.davem@redhat.com \
--to=davem@redhat.com \
--cc=Paul.McKenney@us.ibm.com \
--cc=netdev@oss.sgi.com \
--cc=niv@us.ibm.com \
--cc=shemminger@osdl.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).