From: Jesse Gross <jesse@nicira.com>
To: Cong Wang <xiyou.wangcong@gmail.com>
Cc: netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH net-next v3 6/6] openvswitch: Add vxlan tunneling support.
Date: Thu, 25 Jul 2013 11:19:47 -0700 [thread overview]
Message-ID: <CAEP_g=9K=a0BQPBugkExS_ZGySezohOBi9BUDW8c6dna698fMA@mail.gmail.com> (raw)
In-Reply-To: <ksqhg8$jej$1@ger.gmane.org>
On Wed, Jul 24, 2013 at 11:44 PM, Cong Wang <xiyou.wangcong@gmail.com> wrote:
> On Wed, 24 Jul 2013 at 18:00 GMT, Pravin B Shelar <pshelar@nicira.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.
prev parent reply other threads:[~2013-07-25 18:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-24 18:00 [PATCH net-next v3 6/6] openvswitch: Add vxlan tunneling support Pravin B Shelar
2013-07-25 6:44 ` Cong Wang
2013-07-25 18:19 ` Jesse Gross [this message]
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='CAEP_g=9K=a0BQPBugkExS_ZGySezohOBi9BUDW8c6dna698fMA@mail.gmail.com' \
--to=jesse@nicira.com \
--cc=netdev@vger.kernel.org \
--cc=xiyou.wangcong@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).