netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nivedita Singhvi <niv@us.ibm.com>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: "David S. Miller" <davem@redhat.com>,
	Paul McKenney <Paul.McKenney@us.ibm.com>,
	netdev@oss.sgi.com
Subject: Re: [RFC] Use RCU for fib_rules
Date: Wed, 31 Mar 2004 12:20:56 -0800	[thread overview]
Message-ID: <406B2828.7070800@us.ibm.com> (raw)
In-Reply-To: <20040331112839.02e8d4c2@dell_ss3.pdx.osdl.net>

Stephen Hemminger wrote:

> The IP forwarding rules, uses rwlock when it could use RCU.
> Don't know if this would help or hurt the recent discussions about
> large rulesets and DOS attacks.
> 
> Also, it increases the size of fib_rule slightly.

Stephen,

Any benchmarks or perf tests that quantify the gain here?

thanks,
Nivedita

  reply	other threads:[~2004-03-31 20:20 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 [this message]
2004-03-31 21:05   ` Stephen Hemminger
2004-03-31 21:11     ` David S. Miller
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=406B2828.7070800@us.ibm.com \
    --to=niv@us.ibm.com \
    --cc=Paul.McKenney@us.ibm.com \
    --cc=davem@redhat.com \
    --cc=netdev@oss.sgi.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).