lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Message-ID: <20160823215916.6fd6a57a@halley> Date: Tue, 23 Aug 2016 21:59:16 +0300 From: Shmulik Ladkani <shmulik.ladkani@...il.com> To: Amir Vadai <amir@...ai.me>, Jamal Hadi Salim <jhs@...atatu.com> Cc: "David S. Miller" <davem@...emloft.net>, netdev@...r.kernel.org, John Fastabend <john.r.fastabend@...el.com>, Jiri Pirko <jiri@...lanox.com>, Cong Wang <xiyou.wangcong@...il.com>, Or Gerlitz <ogerlitz@...lanox.com>, Hadar Har-Zion <hadarh@...lanox.com> Subject: Re: [PATCH net-next 3/3] net/sched: Introduce act_iptunnel Hi, On Tue, 23 Aug 2016 19:21:41 +0300 Amir Vadai <amir@...ai.me> wrote: > On Tue, Aug 23, 2016 at 08:37:07AM -0400, Jamal Hadi Salim wrote: > > > > The noun "ip tunnel" is a little misleading. Unless you can use > > this for other types of tunnels (ipip, etc). If this is specific > > for just vxlan and metadata setting then some name like vxlanmeta > > or something else that signifies both metadata de/encap + vxlan would > > be helpful. > Yeh, this name is not the best... > The action is not vxlan specific, it should be good for all the > ip tunnel interfaces that use metadata for the outer headers. > I will rename it to something like mdtunnel - unless someone has a > better suggestion. Well, in bpf we have BPF_FUNC_skb_set_tunnel_key. How about "action tunnel_key" as the noun? Another decent alternative might be "action tunnel_info". Not sure about the verbs though.. "action tunnel_key set/unset"? Regards, Shmulik
Powered by blists - more mailing lists