[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20160216165110.GG2227@nanopsycho.orion>
Date: Tue, 16 Feb 2016 17:51:10 +0100
From: Jiri Pirko <jiri@...nulli.us>
To: Or Gerlitz <ogerlitz@...lanox.com>
Cc: netdev@...r.kernel.org, davem@...emloft.net, idosch@...lanox.com,
eladr@...lanox.com, yotamg@...lanox.com, yishaih@...lanox.com,
dledford@...hat.com, sean.hefty@...el.com,
hal.rosenstock@...il.com, eugenia@...lanox.com,
roopa@...ulusnetworks.com, nikolay@...ulusnetworks.com,
hadarh@...lanox.com, jhs@...atatu.com, john.fastabend@...il.com,
jeffrey.t.kirsher@...el.com, jbenc@...hat.com
Subject: Re: [patch net-next RFC 4/6] mlx4: Implement devlink interface
Tue, Feb 16, 2016 at 05:43:53PM CET, ogerlitz@...lanox.com wrote:
>On 2/3/2016 12:48 PM, Jiri Pirko wrote:
>>Implement newly introduced devlink interface. Add devlink port instances
>>for every port and set the port types accordingly.
>>
>
>Lets see how to use the newly introduced interface in a way which would allow
>us to get a configuration
>profile from user-space and program it to the firmware. This is generic
>problem for other drivers too - we've triedsolving it with configfs in the
>past but the patches were not accepted.
That we plan to do for mlxsw as well via devlink. That will be in a
follow-up patchset.
Powered by blists - more mailing lists