On Wed, Feb 24, 2016 at 08:19:58AM +0100, Jiri Pirko wrote:
> Tue, Feb 23, 2016 at 10:19:48PM CET, ja...@redhat.com wrote:
> >On Tue, Feb 23, 2016 at 04:51:26PM +0100, Jiri Pirko wrote:
> >> From: Jiri Pirko
> >>
> >> Introduce devlink infrastructure for drivers to register and expose to
> >> use
Tue, Feb 23, 2016 at 10:19:48PM CET, ja...@redhat.com wrote:
>On Tue, Feb 23, 2016 at 04:51:26PM +0100, Jiri Pirko wrote:
>> From: Jiri Pirko
>>
>> Introduce devlink infrastructure for drivers to register and expose to
>> userspace via generic Netlink interface.
>>
>> There are two basic objects
On Tue, Feb 23, 2016 at 04:51:26PM +0100, Jiri Pirko wrote:
> From: Jiri Pirko
>
> Introduce devlink infrastructure for drivers to register and expose to
> userspace via generic Netlink interface.
>
> There are two basic objects defined:
> devlink - one instance for every "parent device", for ex
From: Jiri Pirko
Introduce devlink infrastructure for drivers to register and expose to
userspace via generic Netlink interface.
There are two basic objects defined:
devlink - one instance for every "parent device", for example switch ASIC
devlink port - one instance for every physical port of t
