> From: David Miller [mailto:[email protected]] > Sent: Monday, December 3, 2018 11:13 PM > To: [email protected] > Cc: Salil Mehta <[email protected]>; Zhuangyuzeng (Yisen) > <[email protected]>; lipeng (Y) <[email protected]>; > [email protected]; [email protected]; linux- > [email protected]; Linuxarm <[email protected]>; Liuzhongzhu > <[email protected]>; [email protected]; [email protected] > Subject: Re: [RFC net-next 3/9] net: hns3: Add "port vlan table" > information query function > > From: Jakub Kicinski <[email protected]> > Date: Mon, 3 Dec 2018 15:12:22 -0800 > > > On Sun, 2 Dec 2018 23:09:27 +0000, Salil Mehta wrote: > >> From: liuzhongzhu <[email protected]> > >> > >> This patch prints port vlan table information. > >> > >> debugfs command: > >> echo dump port vlan tbl > cmd > >> > >> Sample Command: > >> root@(none)# echo dump port vlan tbl > cmd > >> vlan | port filter bitMap: > >> 0000 | 00000000:00000000:00000000:00000000:00000000:00000001 > >> root@(none)# > >> > >> Signed-off-by: liuzhongzhu <[email protected]> > >> Signed-off-by: Salil Mehta <[email protected]> > > > > 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. Also, on-SoC NIC contains other tables which might not have any standard user-space interface at all. What are your suggestions regarding that? Thanks Salil
