Re: Driver profiles RFC

2017-08-12 Thread Jiri Pirko
Fri, Aug 11, 2017 at 11:57:38PM CEST, kubak...@wp.pl wrote: >On Tue, 8 Aug 2017 16:15:41 +0300, Arkadi Sharshevsky wrote: >> Driver <--> Devlink API >> === >> Each driver will register his resources with default values at init in >> a similar way to DPIPE table registration. In

Re: Driver profiles RFC

2017-08-11 Thread Jakub Kicinski
On Tue, 8 Aug 2017 16:15:41 +0300, Arkadi Sharshevsky wrote: > Driver <--> Devlink API > === > Each driver will register his resources with default values at init in > a similar way to DPIPE table registration. In case those resources already > exist the default values are disca

Re: Driver profiles RFC

2017-08-11 Thread Roopa Prabhu
On Wed, Aug 9, 2017 at 4:43 AM, Arkadi Sharshevsky wrote: > > > On 08/08/2017 07:08 PM, Roopa Prabhu wrote: >> On Tue, Aug 8, 2017 at 6:15 AM, Arkadi Sharshevsky >> wrote: >>> [snip] >>> User Configuration >>> -- >>> Such an UAPI is very low level, and thus an average user may

Re: Driver profiles RFC

2017-08-09 Thread Arkadi Sharshevsky
On 08/08/2017 07:08 PM, Roopa Prabhu wrote: > On Tue, Aug 8, 2017 at 6:15 AM, Arkadi Sharshevsky > wrote: >> Drivers may require driver specific information during the init stage. >> For example, memory based shared resource which should be segmented for >> different ASIC processes, such as FDB

Re: Driver profiles RFC

2017-08-08 Thread Roopa Prabhu
On Tue, Aug 8, 2017 at 6:15 AM, Arkadi Sharshevsky wrote: > Drivers may require driver specific information during the init stage. > For example, memory based shared resource which should be segmented for > different ASIC processes, such as FDB and LPM lookups. > > The current mlxsw implementation

Re: Driver profiles RFC

2017-08-08 Thread Arkadi Sharshevsky
On 08/08/2017 04:54 PM, Andrew Lunn wrote: > On Tue, Aug 08, 2017 at 04:15:41PM +0300, Arkadi Sharshevsky wrote: >> Drivers may require driver specific information during the init stage. >> For example, memory based shared resource which should be segmented for >> different ASIC processes, such a

Re: Driver profiles RFC

2017-08-08 Thread Andrew Lunn
On Tue, Aug 08, 2017 at 04:15:41PM +0300, Arkadi Sharshevsky wrote: > Drivers may require driver specific information during the init stage. > For example, memory based shared resource which should be segmented for > different ASIC processes, such as FDB and LPM lookups. Hi Arkadi Have you looked

Re: Driver profiles RFC

2017-08-08 Thread Jiri Pirko
Tue, Aug 08, 2017 at 03:15:41PM CEST, arka...@mellanox.com wrote: >Drivers may require driver specific information during the init stage. >For example, memory based shared resource which should be segmented for >different ASIC processes, such as FDB and LPM lookups. > >The current mlxsw implementat