From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jakub Kicinski <jakub.kicinski@netronome.com>
Subject: Re: [PATCH net-next 11/18] vxlan: Add netif_is_vxlan()
Date: Mon, 15 Oct 2018 11:57:56 -0700
Message-ID: <20181015115756.13b6c0da@cakuba.netronome.com>
References: <20181013171725.3261-1-idosch@mellanox.com>
	<20181013171725.3261-12-idosch@mellanox.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Cc: "ivecera@redhat.com" <ivecera@redhat.com>,
	"andrew@lunn.ch" <andrew@lunn.ch>,
	"nikolay@cumulusnetworks.com" <nikolay@cumulusnetworks.com>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"roopa@cumulusnetworks.com" <roopa@cumulusnetworks.com>,
	"vivien.didelot@savoirfairelinux.com" <vivien.didelot@savoirfairelinux.com>,
	"f.fainelli@gmail.com,   <bridge@lists.linux-foundation.org>, mlxsw <mlxsw@mellanox.com>,  Jiri Pirko <jiri@mellanox.com>, Petr Machata <petrm@mellanox.com>, " <stephen@networkplumber.org>,
	"bridge@lists.linux-foundation.org,  " davem@davemloft.net " <davem@davemloft.net>, " <f.fainelli@gmail.com>,
	"stephen@networkplumber.org"@mail.linuxfoundation.org
To: Ido Schimmel <idosch@mellanox.com>
Return-path: <bridge-bounces@lists.linux-foundation.org>
In-Reply-To: <20181013171725.3261-12-idosch@mellanox.com>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bridge>,
	<mailto:bridge-request@lists.linux-foundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bridge/>
List-Post: <mailto:bridge@lists.linux-foundation.org>
List-Help: <mailto:bridge-request@lists.linux-foundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bridge>,
	<mailto:bridge-request@lists.linux-foundation.org?subject=subscribe>
Sender: bridge-bounces@lists.linux-foundation.org
Errors-To: bridge-bounces@lists.linux-foundation.org
List-Id: netdev.vger.kernel.org

On Sat, 13 Oct 2018 17:18:38 +0000, Ido Schimmel wrote:
> Add the ability to determine whether a netdev is a VxLAN netdev by
> calling the above mentioned function that checks the netdev's private
> flags.
> 
> This will allow modules to identify netdev events involving a VxLAN
> netdev and act accordingly. For example, drivers capable of VxLAN
> offload will need to configure the underlying device when a VxLAN netdev
> is being enslaved to an offloaded bridge.
> 
> Signed-off-by: Ido Schimmel <idosch@mellanox.com>
> Reviewed-by: Petr Machata <petrm@mellanox.com>

Is this preferable over

!strcmp(netdev->rtnl_link_ops->kind, "vxlan")

which is what TC offloads do?