From: Robert Shearman <rshearma@brocade.com>
To: Roopa Prabhu <roopa@cumulusnetworks.com>, <ebiederm@xmission.com>,
<tgraf@suug.ch>
Cc: <davem@davemloft.net>, <netdev@vger.kernel.org>
Subject: Re: [PATCH net-next RFC v2 0/3] light weight tunnel infrastructure and driver
Date: Fri, 19 Jun 2015 15:38:36 +0100 [thread overview]
Message-ID: <5584296C.1080108@brocade.com> (raw)
In-Reply-To: <1434689355-4088-1-git-send-email-roopa@cumulusnetworks.com>
On 19/06/15 05:49, Roopa Prabhu wrote:
> From: Roopa Prabhu <roopa@cumulusnetworks.com>
>
> This series implements infrastructure for light weight tunnels to support
> mpls label edge routers (ie mpls ip tunnels). As previously discussed
> having netdevices will not scale. Hence this series introduces new RTA_ENCAP*
> attributes to attach encap information with routes (following suggestion
> from Eric Biederman).
Looks promising, thanks for posting this series Roopa!
>
> The first patch introduces an infrastructure to support light weight tunnels
> that dont have netdevices. The infrastructure allows tunnel drivers
> to register handlers to parse and build tunnel encap data which can be attached
> to each route nexthop.
>
> The second patch adds support in ipv4 fib to carry such light weight tunnel
> encap data.
I presume this isn't ready to be merged until IPv6 is done, right?
>
> The third patch implements mpls ip tunnels using this light weight tunnel
> infrastructure.
>
> Could not think of a better name, so, it is 'lwt' for 'light weight tunnels'
> for now.
I can't think of a better name either.
Thanks,
Rob
next prev parent reply other threads:[~2015-06-19 14:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-19 4:49 [PATCH net-next RFC v2 0/3] light weight tunnel infrastructure and driver Roopa Prabhu
2015-06-19 14:38 ` Robert Shearman [this message]
2015-06-19 15:05 ` roopa
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=5584296C.1080108@brocade.com \
--to=rshearma@brocade.com \
--cc=davem@davemloft.net \
--cc=ebiederm@xmission.com \
--cc=netdev@vger.kernel.org \
--cc=roopa@cumulusnetworks.com \
--cc=tgraf@suug.ch \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.