From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Lunn Subject: Re: [RFC net-next 3/9] net: hns3: Add "port vlan table" information query function Date: Tue, 4 Dec 2018 11:55:54 +0100 Message-ID: <20181204105554.GD741@lunn.ch> References: <20181202230933.15560-1-salil.mehta@huawei.com> <20181202230933.15560-4-salil.mehta@huawei.com> <20181203151222.6e56efcd@cakuba.netronome.com> <20181203.151253.1348214769326219632.davem@davemloft.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: David Miller , "jakub.kicinski@netronome.com" , "Zhuangyuzeng (Yisen)" , "lipeng (Y)" , "mehta.salil@opnsrc.net" , "netdev@vger.kernel.org" , "linux-kernel@vger.kernel.org" , Linuxarm , Liuzhongzhu , "jiri@resnulli.us" , "f.fainelli@gmail.com" To: Salil Mehta Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org List-Id: netdev.vger.kernel.org > > > Adding debugfs files for basic switch concepts like MAC and VLAN tables > > > seems like a bit of a stretch to me. I wonder what others think. > > > > Agreed. > > > I was wondering how other vendors are solving this? One way I could > understand is to use "Switchdev" framework which in turn will expose > entries to the kernel using the switch driver. In our NIC we don't > have a proper switch and it cannot learn/age entries. Your hardware is there to accelerate what linux can do in software. How do we manage the software version of this feature? > Also, on-SoC NIC contains other tables which might not have any standard > user-space interface at all. What are your suggestions regarding that? How are these tables map to software features the Linux stack implements? Andrew