netdev - extending ndo_add_rx_vxlan

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Sun, 27 Oct 2013 17:21:51 +0200
From:	Or Gerlitz <ogerlitz@...lanox.com>
To:	Joseph Gasparakis <joseph.gasparakis@...el.com>,
	John Fastabend <john.r.fastabend@...el.com>
CC:	Yan Burman <yanb@...lanox.com>, netdev <netdev@...r.kernel.org>,
	"Stephen Hemminger" <stephen@...workplumber.org>
Subject: extending  ndo_add_rx_vxlan_port

Hi,

So with commit 53cf527513eed6e7170e9dceacd198f9267171b0 "vxlan: Notify 
drivers for listening UDP port changes" drivers that have HW offloads 
for vxlan can be notified on which UDP port to listen. Taking this 
further, some HW may need to know the multicast address and/or the VNID 
used by the vxlan instance/s set above them. In that respect, do we 
prefer to extend ndo_add_rx_vxlan_port() or introduce new ndo?

Or.
--
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