From: David Ahern <dsahern@gmail.com>
To: Carmine Scarpitta <carmine.scarpitta@uniroma2.it>
Cc: davem@davemloft.net, kuznet@ms2.inr.ac.ru,
yoshfuji@linux-ipv6.org, kuba@kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, ahmed.abdelsalam@gssi.it,
dav.lebrun@gmail.com, andrea.mayer@uniroma2.it,
paolo.lungaroni@cnit.it, hiroki.shirokura@linecorp.com
Subject: Re: [net-next 1/2] Perform IPv4 FIB lookup in a predefined FIB table
Date: Fri, 21 Feb 2020 10:31:40 -0700 [thread overview]
Message-ID: <70077e59-1614-b059-a85e-42863f63144f@gmail.com> (raw)
In-Reply-To: <20200220233336.53eda87e7a76ed24317e0165@uniroma2.it>
On 2/20/20 3:33 PM, Carmine Scarpitta wrote:
> As you can see, what is missing is having SRv6 End.DT4 supported to do
> decapsulation and VRF lookup.
Thanks for the detailed explanation and reference. Both this comment and
the slides reference VRF and per-tenant table lookup which is the same
as VRF.
If you allocated a VRF device for the tenant, the SRv6 header pop and
route lookup can be done very similar to how MPLS works when the goal is
to do a route lookup vs forwarding to a specific nexthop, be it main table:
ip -f mpls route add 200 dev lo
or VRF table
ip -f mpls route add 200 dev red
Take a look at the mpls code. Unless I am missing something this use
case is very similar.
next prev parent reply other threads:[~2020-02-21 17:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-13 1:09 [net-next 0/2] Add support for SRv6 End.DT4 action Carmine Scarpitta
2020-02-13 1:09 ` [net-next 1/2] Perform IPv4 FIB lookup in a predefined FIB table Carmine Scarpitta
2020-02-15 18:06 ` David Ahern
2020-02-18 23:50 ` Carmine Scarpitta
2020-02-19 1:05 ` David Ahern
2020-02-19 2:49 ` Carmine Scarpitta
2020-02-19 4:29 ` David Ahern
2020-02-20 22:33 ` Carmine Scarpitta
2020-02-21 17:31 ` David Ahern [this message]
2020-03-06 16:45 ` Ahmed Abdelsalam
2020-03-09 15:36 ` David Ahern
2020-03-10 16:26 ` Ahmed Abdelsalam
2020-02-13 1:09 ` [net-next 2/2] Add support for SRv6 End.DT4 action Carmine Scarpitta
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=70077e59-1614-b059-a85e-42863f63144f@gmail.com \
--to=dsahern@gmail.com \
--cc=ahmed.abdelsalam@gssi.it \
--cc=andrea.mayer@uniroma2.it \
--cc=carmine.scarpitta@uniroma2.it \
--cc=dav.lebrun@gmail.com \
--cc=davem@davemloft.net \
--cc=hiroki.shirokura@linecorp.com \
--cc=kuba@kernel.org \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=paolo.lungaroni@cnit.it \
--cc=yoshfuji@linux-ipv6.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
all inboxes | Powered by JetHome®