netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jiri Benc <jbenc@redhat.com>
To: Pravin Shelar <pshelar@nicira.com>
Cc: netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH net] openvswitch: Fix egress tunnel info.
Date: Tue, 6 Oct 2015 21:32:45 +0200	[thread overview]
Message-ID: <20151006213245.74810d81@griffin> (raw)
In-Reply-To: <CALnjE+rk4d0bfsqu3KMhpYUDqYPzPYkA+ZqS5VU_J_GbAj5p4A@mail.gmail.com>

On Tue, 6 Oct 2015 12:21:24 -0700, Pravin Shelar wrote:
> It should report the flag when device parameters are requested by
> userspace if there is support for lwtunnel. So check for the flag
> should be good enough test for lwtunnel support. Why is that not
> reliable check?

Which device? You'll need to create one before querying it. Which won't
work so nicely for older kernels. Basically, what the user space would
have to do is trying to create a vxlan interface and then deleting it
and going the tunnel vport way. It can be quite confusing, I'm afraid.

 Jiri

-- 
Jiri Benc

  reply	other threads:[~2015-10-06 19:32 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-05 17:58 [PATCH net] openvswitch: Fix egress tunnel info Pravin B Shelar
2015-10-05 18:40 ` Jiri Benc
2015-10-05 19:37   ` Pravin Shelar
2015-10-06 15:56     ` Jiri Benc
2015-10-06 18:28       ` Pravin Shelar
2015-10-06 18:45         ` Jiri Benc
2015-10-06 18:55           ` Pravin Shelar
2015-10-06 19:03             ` Jiri Benc
2015-10-06 19:21               ` Pravin Shelar
2015-10-06 19:32                 ` Jiri Benc [this message]
2015-10-06 21:16                   ` Pravin Shelar
2015-10-07  8:09                     ` Jiri Benc
2015-10-07  9:34                       ` Thomas Graf
2015-10-07  9:53                         ` Jiri Benc
2015-10-07 17:19                       ` Pravin Shelar
2015-10-06 15:42 ` Jiri Benc
2015-10-06 18:26   ` Pravin Shelar
2015-10-06 18:55     ` Jiri Benc
2015-10-06 19:11       ` Pravin Shelar

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=20151006213245.74810d81@griffin \
    --to=jbenc@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=pshelar@nicira.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).