[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <F4CC6FACFEB3C54C9141D49AD221F7F93C06855D@FRAEML521-MBX.china.huawei.com>
Date: Tue, 4 Dec 2018 10:10:32 +0000
From: Salil Mehta <salil.mehta@...wei.com>
To: David Miller <davem@...emloft.net>,
"jakub.kicinski@...ronome.com" <jakub.kicinski@...ronome.com>
CC: "Zhuangyuzeng (Yisen)" <yisen.zhuang@...wei.com>,
"lipeng (Y)" <lipeng321@...wei.com>,
"mehta.salil@...src.net" <mehta.salil@...src.net>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Linuxarm <linuxarm@...wei.com>,
Liuzhongzhu <liuzhongzhu@...wei.com>,
"jiri@...nulli.us" <jiri@...nulli.us>,
"f.fainelli@...il.com" <f.fainelli@...il.com>
Subject: RE: [RFC net-next 3/9] net: hns3: Add "port vlan table" information
query function
> From: David Miller [mailto:davem@...emloft.net]
> Sent: Monday, December 3, 2018 11:13 PM
> To: jakub.kicinski@...ronome.com
> Cc: Salil Mehta <salil.mehta@...wei.com>; Zhuangyuzeng (Yisen)
> <yisen.zhuang@...wei.com>; lipeng (Y) <lipeng321@...wei.com>;
> mehta.salil@...src.net; netdev@...r.kernel.org; linux-
> kernel@...r.kernel.org; Linuxarm <linuxarm@...wei.com>; Liuzhongzhu
> <liuzhongzhu@...wei.com>; jiri@...nulli.us; f.fainelli@...il.com
> Subject: Re: [RFC net-next 3/9] net: hns3: Add "port vlan table"
> information query function
>
> From: Jakub Kicinski <jakub.kicinski@...ronome.com>
> Date: Mon, 3 Dec 2018 15:12:22 -0800
>
> > On Sun, 2 Dec 2018 23:09:27 +0000, Salil Mehta wrote:
> >> From: liuzhongzhu <liuzhongzhu@...wei.com>
> >>
> >> 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 <liuzhongzhu@...wei.com>
> >> Signed-off-by: Salil Mehta <salil.mehta@...wei.com>
> >
> > 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
Powered by blists - more mailing lists