[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJ3xEMiBhTiJFv_znngAg3+REk38w_3G-dr8rXCmGYeT2xketg@mail.gmail.com>
Date: Wed, 2 Dec 2015 10:21:37 +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 would be currently supported,
bonding vlans or vlan a bond?
bond b0 -->
vlan A.X --> switchdev port A
vlan B.X --> switchdev port B
vlan b0.X --> bond b0 -->
vlan --> switchdev port
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
Powered by blists - more mailing lists