From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Graf Subject: Re: [patch net-next RFC 0/4] introduce infrastructure for support of switch chip datapath Date: Thu, 27 Mar 2014 16:59:01 +0000 Message-ID: <20140327165901.GB13573@casper.infradead.org> References: <20140326165934.GH2869@minipsycho.orion> <20140326173536.GJ2869@minipsycho.orion> <20140326181436.GL2869@minipsycho.orion> <53334BDA.1060608@mojatatu.com> <20140327065616.GA2845@minipsycho.orion> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Sergey Ryazanov , Jiri Pirko , Jamal Hadi Salim , Roopa Prabhu , Neil Horman , netdev , David Miller , Andy Gospodarek , dborkman , ogerlitz , jesse , pshelar , azhou , Ben Hutchings , Stephen Hemminger , jeffrey.t.kirsher@intel.com, vyasevic , Cong Wang , John Fastabend , Eric Dumazet , Scott Feldman , Lennert Buytenhek , Shrijeet Mukherjee , Felix Fietkau To: Florian Fainelli Return-path: Received: from casper.infradead.org ([85.118.1.10]:53516 "EHLO casper.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755469AbaC0Q7G (ORCPT ); Thu, 27 Mar 2014 12:59:06 -0400 Content-Disposition: inline In-Reply-To: Sender: netdev-owner@vger.kernel.org List-ID: On 03/27/14 at 09:41am, Florian Fainelli wrote: > 2014-03-27 7:10 GMT-07:00 Sergey Ryazanov : > > So there are no reasons > > to force user to configure this port manually, and automatic > > configuration of CPU switch port without exporting them as netdev > > seems as good approach. > > Well, maybe that's the answer, since we know that e.g: sw1p3 is always > connected to e.g: eth0, we could create an automatic bridge between > those two, this would keep the netdev exposure to user-space, but an > user would not have to know about that specific detail to get things > to work. I like this approach. It provides visibility without additional configuration burdgen.