netdev - Re: [patch net-next 00/26] bonding/team offload + mlxsw implementation

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-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAJ3xEMgLti3KWEZoB4vp11gy=-xfveThf99K9x-3ZtMjdRMqCg@mail.gmail.com>
Date:	Wed, 2 Dec 2015 10:25:14 +0200
From:	Or Gerlitz <gerlitz.or@...il.com>
To:	Jiri Pirko <jiri@...nulli.us>
Cc:	Linux Netdev List <netdev@...r.kernel.org>,
	David Miller <davem@...emloft.net>,
	Ido Schimmel <idosch@...lanox.com>,
	Elad Raz <eladr@...lanox.com>, yotamg@...lanox.com,
	Or Gerlitz <ogerlitz@...lanox.com>, pjonnala@...adcom.com,
	Jay Vosburgh <j.vosburgh@...il.com>, vfalico@...il.com,
	Andy Gospodarek <gospo@...ulusnetworks.com>,
	Florian Fainelli <f.fainelli@...il.com>,
	Scott Feldman <sfeldma@...il.com>,
	john fastabend <john.fastabend@...il.com>
Subject: Re: [patch net-next 00/26] bonding/team offload + mlxsw implementation

On Wed, Dec 2, 2015 at 9:58 AM, Jiri Pirko <jiri@...nulli.us> wrote:
> Wed, Dec 02, 2015 at 06:53:35AM CET, gerlitz.or@...il.com wrote:

>>Another question relates to users bonding/teaming netdevice ports from
>>different HW switches, or of two vlans over ports from the same HW switch.

>>This is something that AFAIK not supported by HW -- do we want to
>>disallow that?
>>what layer in the kernel we want to enforce that limitation? team/bond
>>or switchdev core or the switchdev HW driver?


> It is not handled at the moment. In can be easily disallowed by driver.

what about the case of LAG + VLANs, what you think fits better HW switches?
what would be currently supported, bonding vlans or vlan a bond?

For me the 1st one (below) makes more sense

bond b0 -->
     vlan A.X --> switchdev port A
     vlan B.X --> switchdev port B

vlan b0.X --> bond b0 -->
                      switchdev port A
                      switchdev port B

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