[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJZOPZLAg+5dYS=bUCkDMyYq8EmA_uvEv1Zi+drq6Qqe5onrzQ@mail.gmail.com>
Date: Mon, 28 Oct 2013 09:35:29 +0200
From: Or Gerlitz <or.gerlitz@...il.com>
To: Joseph Gasparakis <joseph.gasparakis@...el.com>
Cc: Or Gerlitz <ogerlitz@...lanox.com>,
John Fastabend <john.r.fastabend@...el.com>,
Yan Burman <yanb@...lanox.com>,
netdev <netdev@...r.kernel.org>,
Stephen Hemminger <stephen@...workplumber.org>
Subject: Re: extending ndo_add_rx_vxlan_port
On Mon, Oct 28, 2013 at 1:44 AM, Joseph Gasparakis wrote:
> VXLAN implementation is not done like VLAN. VLANs are stacked on top of
> real interfaces and what you are saying makes sense. VXLAN however is
> using ip[6]_tunnel_xmit, and this is why we need to notify all the
As the name of the ndo you added ndo_add_rx_vxlan_port suggests -- HW
needs that for RX offloads. So basically, what I am saying is: in a
similar manner that we already program the NIC "over which" the vxlan
instance is set to listen on the multicast address which is associated
with that vxlan segement, lets give them a hint that packets arriving
on this group are vxlan ones, so they can use it for programming
steering rules.
> netdevs in the system that implement the add/del vxlan port ndo (i.e. are
> capable of offloading inner csums). In effect all physical "real" netdevs
> are candidates to receive/transmit VXLAN traffic, subject to routing
> tables changing or not.
--
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
Powered by blists - more mailing lists