Mon, Apr 15, 2019 at 05:07:04PM CEST, dsah...@gmail.com wrote:
>On 4/14/19 11:41 PM, Jiri Pirko wrote:
>> Mon, Apr 15, 2019 at 04:24:24AM CEST, dsah...@gmail.com wrote:
>>> On 4/13/19 10:20 AM, Jiri Pirko wrote:
From: Jiri Pirko
Currently there is one devlink instance created per ne
On 4/14/19 11:41 PM, Jiri Pirko wrote:
> Mon, Apr 15, 2019 at 04:24:24AM CEST, dsah...@gmail.com wrote:
>> On 4/13/19 10:20 AM, Jiri Pirko wrote:
>>> From: Jiri Pirko
>>>
>>> Currently there is one devlink instance created per network namespace.
>>> That is quite odd considering the fact that devl
Mon, Apr 15, 2019 at 04:24:24AM CEST, dsah...@gmail.com wrote:
>On 4/13/19 10:20 AM, Jiri Pirko wrote:
>> From: Jiri Pirko
>>
>> Currently there is one devlink instance created per network namespace.
>> That is quite odd considering the fact that devlink instance should
>> represent an ASIC. The
On 4/13/19 10:20 AM, Jiri Pirko wrote:
> From: Jiri Pirko
>
> Currently there is one devlink instance created per network namespace.
> That is quite odd considering the fact that devlink instance should
> represent an ASIC. The following patches are going to move the devlink
> instance even more
From: Jiri Pirko
Currently there is one devlink instance created per network namespace.
That is quite odd considering the fact that devlink instance should
represent an ASIC. The following patches are going to move the devlink
instance even more down to a bus device, but until then, have one
devl
