Thu, Apr 05, 2018 at 11:06:41PM CEST, d...@cumulusnetworks.com wrote: >On 4/5/18 2:10 PM, David Ahern wrote: >> >> The ASIC here is the kernel tables in a namespace. It does not make >> sense to have 2 devlink instances for a single namespace. > >I put this example controller in netdevsim per a suggestion from Ido. >The netdevsim seemed like a good idea given that modules intention -- >testing network facilities. Perhaps I should have done this as a >completely standalone module ... > >The intention is to treat the kernel's tables *per namespace* as a >standalone entity that can be managed very similar to ASIC resources.
So you say you want to treat a namespace as an ASIC? That sounds very odd to me :/ >Given that I can add a resource controller module >(drivers/net/kern_res_mgr.c?) that creates a 'struct device' per network >namespace with a devlink instance. In this case the device would very >much be tied to the namespace 1:1. That sounds more reasonable and accurate, yet still odd. You would not have any netdevices there? Any ports?
