From: Benjamin LaHaise <bcrl@kvack.org>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH] fib_semantics: prevent long hash chains in access server config
Date: Sun, 13 Jan 2008 12:58:49 -0500 [thread overview]
Message-ID: <20080113175849.GC12775@kvack.org> (raw)
In-Reply-To: <20080112.213857.68003780.davem@davemloft.net>
On Sat, Jan 12, 2008 at 09:38:57PM -0800, David Miller wrote:
> And guess why we don't do this? Because it's not part of
> the key. Other aspects of the base fib_info and nexthops
> provide the uniqueness, not the devindex of the first hop.
>
> So you'll need to find another way to do this.
Ah, you're right indeed. It's probably easier for me to change how the
daemon adds the local ip address for these point to point interfaces.
-ben
--
"Time is of no importance, Mr. President, only life is important."
Don't Email: <zyntrop@kvack.org>.
next prev parent reply other threads:[~2008-01-13 17:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-12 18:58 [PATCH] fib_semantics: prevent long hash chains in access server config Benjamin LaHaise
2008-01-13 5:38 ` David Miller
2008-01-13 17:58 ` Benjamin LaHaise [this message]
2008-01-14 2:11 ` David Miller
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=20080113175849.GC12775@kvack.org \
--to=bcrl@kvack.org \
--cc=davem@davemloft.net \
--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).