From: Stephen Hemminger <shemminger@vyatta.com>
To: Benjamin LaHaise <bcrl@lhnet.ca>
Cc: netdev@vger.kernel.org
Subject: Re: [RFC PATCH] fib_hash: improve route deletion scaling on interface drop with lots of interfaces
Date: Mon, 26 Oct 2009 17:24:14 -0700 [thread overview]
Message-ID: <20091026172414.34f66f9f@nehalam> (raw)
In-Reply-To: <20091027000302.GA3141@kvack.org>
On Mon, 26 Oct 2009 20:03:02 -0400
Benjamin LaHaise <bcrl@lhnet.ca> wrote:
> Hi folks,
>
> Below is a patch to improve the scaling of interface destruction in
> fib_hash. The general idea is to tie the fib_alias structure into a
> list off of net_device and walk that list during a fib_flush() caused
> by an interface drop. This makes the resulting flush only have to walk
> the number of routes attached to an interface rather than the number of
> routes attached to all interfaces at the expense of a couple of additional
> pointers in struct fib_alias.
>
> This patch is against Linus' tree. I'll post against net-next after a
> bit more testing and feedback. With 20,000 interfaces & routes, interface
> deletion time improves from 53s to 40s. Note that this is with other changes
> applied to improve sysfs and procfs scaling, as otherwise those are the
> bottleneck. Next up in the network code is rt_cache_flush(). Comments?
>
> -ben
>
Any one doing large number of interfaces should be using FIB_TRIE?
--
next prev parent reply other threads:[~2009-10-27 0:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-27 0:03 [RFC PATCH] fib_hash: improve route deletion scaling on interface drop with lots of interfaces Benjamin LaHaise
2009-10-27 0:17 ` David Miller
2009-10-27 14:24 ` Benjamin LaHaise
2009-10-28 1:01 ` David Miller
2009-10-27 0:24 ` Stephen Hemminger [this message]
2009-10-27 21:07 ` Julian Anastasov
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=20091026172414.34f66f9f@nehalam \
--to=shemminger@vyatta.com \
--cc=bcrl@lhnet.ca \
--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).