netdev - Re: [PATCH net-next v3 6/6] openvswitch: Add vxlan tunneling support.

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CAEP_g=9K=a0BQPBugkExS_ZGySezohOBi9BUDW8c6dna698fMA@mail.gmail.com>
Date:	Thu, 25 Jul 2013 11:19:47 -0700
From:	Jesse Gross <jesse@...ira.com>
To:	Cong Wang <xiyou.wangcong@...il.com>
Cc:	netdev <netdev@...r.kernel.org>
Subject: Re: [PATCH net-next v3 6/6] openvswitch: Add vxlan tunneling support.

On Wed, Jul 24, 2013 at 11:44 PM, Cong Wang <xiyou.wangcong@...il.com> wrote:
> On Wed, 24 Jul 2013 at 18:00 GMT, Pravin B Shelar <pshelar@...ira.com> wrote:
>> +
>> +config OPENVSWITCH_VXLAN
>> +     bool "Open vSwitch VXLAN tunneling support"
>> +     depends on INET
>> +     depends on OPENVSWITCH
>> +     depends on VXLAN && !(OPENVSWITCH=y && VXLAN=m)
>
> This seems ugly, is it possible to make these vxlan code be a library as
> iptunnel code?

The goal of separating things out this way is to provide nice layering
between the protocol code and the consumers. There needs to be some
interface between OVS and the tunnel code that straddles the boundary
and putting it in OVS makes the most sense from a hierarchy
perspective.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html