From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jiri Benc Subject: Re: [PATCH net] openvswitch: Fix egress tunnel info. Date: Tue, 6 Oct 2015 21:32:45 +0200 Message-ID: <20151006213245.74810d81@griffin> References: <1444067897-1951-1-git-send-email-pshelar@nicira.com> <20151005204020.56f50496@griffin> <20151006175634.200d69a0@griffin> <20151006204558.5f2f56fc@griffin> <20151006210358.65750aeb@griffin> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: netdev To: Pravin Shelar Return-path: Received: from mx1.redhat.com ([209.132.183.28]:35132 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752995AbbJFTct (ORCPT ); Tue, 6 Oct 2015 15:32:49 -0400 In-Reply-To: Sender: netdev-owner@vger.kernel.org List-ID: 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