From: David Ahern <dsa@cumulusnetworks•com>
To: David Miller <davem@davemloft•net>
Cc: netdev@vger•kernel.org
Subject: Re: [PATCH net-next] net: Support ip route get via given table
Date: Thu, 3 Sep 2015 17:25:59 -0600 [thread overview]
Message-ID: <55E8D707.7010309@cumulusnetworks.com> (raw)
In-Reply-To: <20150903.154015.1172003362734952780.davem@davemloft.net>
On 9/3/15 4:40 PM, David Miller wrote:
> From: David Ahern <dsa@cumulusnetworks•com>
> Date: Wed, 2 Sep 2015 12:03:12 -0700
>
>> Add support for 'ip [-6] route get table X' where the user wants to
>> force the FIB lookup from a given table.
>>
>> Signed-off-by: David Ahern <dsa@cumulusnetworks•com>
>
> As Thomas mentioned, this adds cost to the FIB lookup fastpath
> for a control-plane only feature, which is really undesirable.
>
> I think I'll pass on this change for now, sorry.
>
Got it. I had other ideas on how to implement it. Figured I would start
with the simplest.
prev parent reply other threads:[~2015-09-03 23:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-02 19:03 [PATCH net-next] net: Support ip route get via given table David Ahern
2015-09-02 19:12 ` Thomas Graf
2015-09-02 19:22 ` David Ahern
2015-09-02 19:38 ` Thomas Graf
2015-09-02 19:50 ` David Ahern
2015-09-03 22:40 ` David Miller
2015-09-03 23:25 ` David Ahern [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=55E8D707.7010309@cumulusnetworks.com \
--to=dsa@cumulusnetworks$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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