From: David Miller <davem@davemloft.net>
To: shemminger@vyatta.com
Cc: eric.dumazet@gmail.com, netdev@vger.kernel.org
Subject: Re: [PATCH] ipv4: Remove fib_hash.
Date: Wed, 02 Feb 2011 13:51:05 -0800 (PST) [thread overview]
Message-ID: <20110202.135105.71107300.davem@davemloft.net> (raw)
In-Reply-To: <20110202082921.7eee82e0@nehalam>
From: Stephen Hemminger <shemminger@vyatta.com>
Date: Wed, 2 Feb 2011 08:29:21 -0800
> For the case of small devices, what about keeping fib_hash as option
> under CONFIG_EMBEDDED. And remove all the magic resizing of hash table.
> Get back to something with really small size.
That's still going to be ~20,000 lines of code kept in the tree
duplicating functionality.
Sorry, no.
prev parent reply other threads:[~2011-02-02 21:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-01 23:19 [PATCH] ipv4: Remove fib_hash David Miller
2011-02-01 23:26 ` Stephen Hemminger
2011-02-01 23:33 ` Stephen Hemminger
2011-02-01 23:35 ` David Miller
2011-02-02 0:48 ` Eric Dumazet
2011-02-02 2:15 ` David Miller
2011-02-02 16:29 ` Stephen Hemminger
2011-02-02 21:51 ` David Miller [this message]
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=20110202.135105.71107300.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=shemminger@vyatta.com \
/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).