From: roopa <roopa-qUQiAmfTcIp+XZJcv9eMoEEOCMrvLtNR@public•gmane.org>
To: thomas.morin-C0LM0jrOve7QT0dZR+AlfA@public•gmane.org
Cc: marcelo.leitner-Re5JQEeQqe8AvxtiuMwx3w@public•gmane.org,
edumazet-hpIqsD4AKlfQT0dZR+AlfA@public•gmane.org,
ast-uqk4Ao+rVK5Wk0Htik3J/w@public•gmane.org,
dev-yBygre7rU0TnMu66kgdUjQ@public•gmane.org,
daniel-FeC+5ew28dpmcu3hnIyYJQ@public•gmane.org,
ja-FgGsKACvmQM@public•gmane.org,
simon.horman-wFxRvT7yatFl57MIdRCFDg@public•gmane.org,
jiri-rHqAuBHg3fBzbRFIqnYvSA@public•gmane.org,
hannes-tFNcAqjVMyqKXQKiL6tip0B+6BGkLq7r@public•gmane.org,
tom-BjP2VixgY4xUbtYUoyoikg@public•gmane.org,
netdev-u79uwXL29TY76Z2rM5mHXA@public•gmane.org,
davem-fT/PcQaiUtIeIZ0/mPfg9Q@public•gmane.org,
stephen-OTpzqLSitTUnbdJkjeBofR2eb7JE58TQ@public•gmane.org,
ebiederm-aS9lmoZGLiVWk0Htik3J/w@public•gmane.org,
weichunc-uqk4Ao+rVK5Wk0Htik3J/w@public•gmane.org,
rshearma-43mecJUBy8ZBDgjK7y7TUQ@public•gmane.org,
kaber-dcUjhNyLwpNeoWH0uzbU5w@public•gmane.org
Subject: Re: [PATCH net-next 00/22 v2] Lightweight & flow based encapsulation
Date: Wed, 22 Jul 2015 08:43:58 -0700 [thread overview]
Message-ID: <55AFBA3E.80209@cumulusnetworks.com> (raw)
In-Reply-To: <17034_1437555506_55AF5B32_17034_5736_1_55AF5B30.8070208-C0LM0jrOve7QT0dZR+AlfA@public.gmane.org>
On 7/22/15, 1:58 AM, thomas.morin@orange•com wrote:
> Hi Thomas,
>
> This looks promising.
>
> One question: will this approach allow MPLS-in-GRE and MPLS-in-UDP ?
>
The current series was focused on IP to MPLS tunnels. But, the
infrastructure allows associating encap state with routes and calling
the respective encapsulation output handlers.
For MPLS-in-GRE and MPLS-in-UDP, it appears that MPLS LSP routes
(af_mpls.c) could support associating GRE and UDP encap info (RTA_ENCAP
and RTA_ENCAP_TYPE) similar to IP routes and the re-direction from MPLS
to GRE or MPLS to UDP can be achieved in a similar way using the same
infrastructure.
Thanks,
Roopa
_______________________________________________
dev mailing list
dev@openvswitch•org
http://openvswitch.org/mailman/listinfo/dev
next prev parent reply other threads:[~2015-07-22 15:43 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-21 8:43 [PATCH net-next 00/22 v2] Lightweight & flow based encapsulation Thomas Graf
2015-07-21 8:43 ` [PATCH net-next 01/22] rtnetlink: introduce new RTA_ENCAP_TYPE and RTA_ENCAP attributes Thomas Graf
[not found] ` <cover.1437468140.git.tgraf-G/eBtMaohhA@public.gmane.org>
2015-07-21 8:43 ` [PATCH net-next 02/22] lwtunnel: infrastructure for handling light weight tunnels like mpls Thomas Graf
2015-07-21 8:43 ` [PATCH net-next 03/22] ipv4: support for fib route lwtunnel encap attributes Thomas Graf
2015-07-21 8:43 ` [PATCH net-next 04/22] ipv6: " Thomas Graf
2015-07-21 8:43 ` [PATCH net-next 05/22] lwtunnel: support dst output redirect function Thomas Graf
2015-07-21 8:43 ` [PATCH net-next 06/22] ipv4: redirect dst output to lwtunnel output Thomas Graf
2015-07-21 8:43 ` [PATCH net-next 12/22] dst: Metadata destinations Thomas Graf
2015-07-22 8:58 ` [PATCH net-next 00/22 v2] Lightweight & flow based encapsulation thomas.morin-C0LM0jrOve7QT0dZR+AlfA
[not found] ` <17034_1437555506_55AF5B32_17034_5736_1_55AF5B30.8070208-C0LM0jrOve7QT0dZR+AlfA@public.gmane.org>
2015-07-22 15:43 ` roopa [this message]
2015-07-21 8:43 ` [PATCH net-next 07/22] ipv6: rt6_info output redirect to tunnel output Thomas Graf
2015-07-21 8:43 ` [PATCH net-next 08/22] mpls: export mpls functions for use by mpls iptunnels Thomas Graf
2015-07-21 8:43 ` [PATCH net-next 09/22] mpls: ip tunnel support Thomas Graf
2015-07-21 8:43 ` [PATCH net-next 10/22] ip_tunnel: Make ovs_tunnel_info and ovs_key_ipv4_tunnel generic Thomas Graf
2015-07-21 8:43 ` [PATCH net-next 11/22] icmp: Don't leak original dst into ip_route_input() Thomas Graf
2015-07-21 8:43 ` [PATCH net-next 13/22] arp: Inherit metadata dst when creating ARP requests Thomas Graf
2015-07-21 8:43 ` [PATCH net-next 14/22] vxlan: Flow based tunneling Thomas Graf
2015-07-21 17:30 ` Alexei Starovoitov
2015-07-21 17:53 ` Thomas Graf
2015-07-21 8:43 ` [PATCH net-next 15/22] route: Extend flow representation with tunnel key Thomas Graf
2015-07-21 8:44 ` [PATCH net-next 16/22] route: Per route IP tunnel metadata via lightweight tunnel Thomas Graf
2015-07-21 8:44 ` [PATCH net-next 17/22] fib: Add fib rule match on tunnel id Thomas Graf
2015-07-21 8:44 ` [PATCH net-next 18/22] vxlan: Factor out device configuration Thomas Graf
2015-07-21 8:44 ` [PATCH net-next 19/22] openvswitch: Make tunnel set action attach a metadata dst Thomas Graf
2015-07-21 8:44 ` [PATCH net-next 20/22] openvswitch: Move dev pointer into vport itself Thomas Graf
2015-07-21 8:44 ` [PATCH net-next 21/22] openvswitch: Abstract vport name through ovs_vport_name() Thomas Graf
2015-07-21 8:44 ` [PATCH net-next 22/22] openvswitch: Use regular VXLAN net_device device Thomas Graf
2015-07-21 17:39 ` [PATCH net-next 00/22 v2] Lightweight & flow based encapsulation 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=55AFBA3E.80209@cumulusnetworks.com \
--to=roopa-quqiamftcip+xzjcv9emoeeocmrvltnr@public$(echo .)gmane.org \
--cc=ast-uqk4Ao+rVK5Wk0Htik3J/w@public$(echo .)gmane.org \
--cc=daniel-FeC+5ew28dpmcu3hnIyYJQ@public$(echo .)gmane.org \
--cc=davem-fT/PcQaiUtIeIZ0/mPfg9Q@public$(echo .)gmane.org \
--cc=dev-yBygre7rU0TnMu66kgdUjQ@public$(echo .)gmane.org \
--cc=ebiederm-aS9lmoZGLiVWk0Htik3J/w@public$(echo .)gmane.org \
--cc=edumazet-hpIqsD4AKlfQT0dZR+AlfA@public$(echo .)gmane.org \
--cc=hannes-tFNcAqjVMyqKXQKiL6tip0B+6BGkLq7r@public$(echo .)gmane.org \
--cc=ja-FgGsKACvmQM@public$(echo .)gmane.org \
--cc=jiri-rHqAuBHg3fBzbRFIqnYvSA@public$(echo .)gmane.org \
--cc=kaber-dcUjhNyLwpNeoWH0uzbU5w@public$(echo .)gmane.org \
--cc=marcelo.leitner-Re5JQEeQqe8AvxtiuMwx3w@public$(echo .)gmane.org \
--cc=netdev-u79uwXL29TY76Z2rM5mHXA@public$(echo .)gmane.org \
--cc=rshearma-43mecJUBy8ZBDgjK7y7TUQ@public$(echo .)gmane.org \
--cc=simon.horman-wFxRvT7yatFl57MIdRCFDg@public$(echo .)gmane.org \
--cc=stephen-OTpzqLSitTUnbdJkjeBofR2eb7JE58TQ@public$(echo .)gmane.org \
--cc=thomas.morin-C0LM0jrOve7QT0dZR+AlfA@public$(echo .)gmane.org \
--cc=tom-BjP2VixgY4xUbtYUoyoikg@public$(echo .)gmane.org \
--cc=weichunc-uqk4Ao+rVK5Wk0Htik3J/w@public$(echo .)gmane.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