[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <56C351C9.9010203@mellanox.com>
Date: Tue, 16 Feb 2016 18:43:53 +0200
From: Or Gerlitz <ogerlitz@...lanox.com>
To: Jiri Pirko <jiri@...nulli.us>
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
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.
Or.
Powered by blists - more mailing lists