From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Lunn Subject: Re: [PATCH 0/4] RFC CPSW switchdev mode Date: Thu, 24 May 2018 14:54:31 +0200 Message-ID: <20180524125431.GB24557@lunn.ch> References: <1527144984-31236-1-git-send-email-ilias.apalodimas@linaro.org> <20180524080528.GD2295@nanopsycho> <20180524084831.GA2759@apalos> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Jiri Pirko , netdev@vger.kernel.org, grygorii.strashko@ti.com, ivan.khoronzhuk@linaro.org, nsekhar@ti.com, ivecera@redhat.com, francois.ozog@linaro.org, yogeshs@ti.com, spatton@ti.com To: Ilias Apalodimas Return-path: Received: from vps0.lunn.ch ([185.16.172.187]:43525 "EHLO vps0.lunn.ch" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S964789AbeEXMye (ORCPT ); Thu, 24 May 2018 08:54:34 -0400 Content-Disposition: inline In-Reply-To: <20180524084831.GA2759@apalos> Sender: netdev-owner@vger.kernel.org List-ID: On Thu, May 24, 2018 at 11:48:31AM +0300, Ilias Apalodimas wrote: > On Thu, May 24, 2018 at 10:05:28AM +0200, Jiri Pirko wrote: > > Thu, May 24, 2018 at 08:56:20AM CEST, ilias.apalodimas@linaro.org wrote: > > Any reason you need cpu port? We don't need it in mlxsw and also in dsa. > Yes i've seen that on mlxsw/rocker drivers and i was reluctant adding one here. > The reason is that TI wants this configured differently from customer facing > ports. Apparently there are existing customers already using the "feature". > So OR'ing and adding the cpu port on every operation (add/del vlans add > ucast/mcast entries etc) was less favoured. Hi Ilias Nice to see this device moving away from its custom model and towards the switchdev model. Did you consider making a clean break from the existing code and write a new driver. Let the existing customers using the existing driver. Have the new switchdev driver fully conform to switchdev. I don't like having this 'cpu' interface. As you say, it breaks the switchhdev model. If we need to extend the switchdev model to support some use case, lets do that. Please can you fully describe the use cases, so we can discuss how to implement them cleanly within the switchdev model. Thanks Andrew