Re: [patch net-next RFC 0/6] Introduce devlink interface and first drivers to use it

2016-02-08 Thread Doug Ledford
On 02/07/2016 03:18 PM, roopa wrote: > On 2/3/16, 2:47 AM, Jiri Pirko wrote: >> From: Jiri Pirko >> >> There a is need for some userspace API that would allow to expose things >> that are not directly related to any device class like net_device of >> ib_device, but rather chip-wide/switch-ASIC-wid

Re: [patch net-next RFC 0/6] Introduce devlink interface and first drivers to use it

2016-02-08 Thread Hannes Frederic Sowa
Hi, On 08.02.2016 11:55, Jiri Pirko wrote: Mon, Feb 08, 2016 at 11:15:38AM CET, han...@stressinduktion.org wrote: Hello, On 06.02.2016 20:40, Jiri Pirko wrote: Fri, Feb 05, 2016 at 06:38:42PM CET, alexei.starovoi...@gmail.com wrote: On Fri, Feb 05, 2016 at 11:01:22AM +0100, Hannes Frederic S

Re: [patch net-next RFC 0/6] Introduce devlink interface and first drivers to use it

2016-02-08 Thread Jiri Pirko
Mon, Feb 08, 2016 at 11:15:38AM CET, han...@stressinduktion.org wrote: >Hello, > >On 06.02.2016 20:40, Jiri Pirko wrote: >>Fri, Feb 05, 2016 at 06:38:42PM CET, alexei.starovoi...@gmail.com wrote: >>>On Fri, Feb 05, 2016 at 11:01:22AM +0100, Hannes Frederic Sowa wrote: Okay. I see it more a

Re: [patch net-next RFC 0/6] Introduce devlink interface and first drivers to use it

2016-02-08 Thread Hannes Frederic Sowa
Hello, On 06.02.2016 20:40, Jiri Pirko wrote: Fri, Feb 05, 2016 at 06:38:42PM CET, alexei.starovoi...@gmail.com wrote: On Fri, Feb 05, 2016 at 11:01:22AM +0100, Hannes Frederic Sowa wrote: Okay. I see it more as changing mode of operation of hardware and thus has not really anything to do wit

Re: [patch net-next RFC 0/6] Introduce devlink interface and first drivers to use it

2016-02-07 Thread roopa
On 2/3/16, 2:47 AM, Jiri Pirko wrote: > From: Jiri Pirko > > There a is need for some userspace API that would allow to expose things > that are not directly related to any device class like net_device of > ib_device, but rather chip-wide/switch-ASIC-wide stuff. > > Use cases: > 1) get/set of port

Re: [patch net-next RFC 0/6] Introduce devlink interface and first drivers to use it

2016-02-06 Thread Jiri Pirko
Fri, Feb 05, 2016 at 06:38:42PM CET, alexei.starovoi...@gmail.com wrote: >On Fri, Feb 05, 2016 at 11:01:22AM +0100, Hannes Frederic Sowa wrote: >> >> Okay. I see it more as changing mode of operation of hardware and thus has >> not really anything to do with networking. If you say you change ether

Re: [patch net-next RFC 0/6] Introduce devlink interface and first drivers to use it

2016-02-05 Thread Alexei Starovoitov
On Fri, Feb 05, 2016 at 11:01:22AM +0100, Hannes Frederic Sowa wrote: > > Okay. I see it more as changing mode of operation of hardware and thus has > not really anything to do with networking. If you say you change ethernet to > infiniband it has something to do with networking, sure. But I am fi

Re: [patch net-next RFC 0/6] Introduce devlink interface and first drivers to use it

2016-02-05 Thread Jesper Dangaard Brouer
On Thu, 4 Feb 2016 19:01:55 + "Rosen, Rami" wrote: > Hi, > > >Btw, if you add this tool into iproute2 (which would be preferred), >then > >probably dl should be ok (and easier retrievable in that relation). > > +1. > > This tool, which uses netlink messages, seems a natural candidate for

Re: [patch net-next RFC 0/6] Introduce devlink interface and first drivers to use it

2016-02-05 Thread Hannes Frederic Sowa
On 04.02.2016 14:26, Jiri Pirko wrote: Thu, Feb 04, 2016 at 02:22:17PM CET, han...@stressinduktion.org wrote: On 03.02.2016 16:17, Daniel Borkmann wrote: On 02/03/2016 02:33 PM, Jiri Pirko wrote: Wed, Feb 03, 2016 at 02:31:33PM CET, bro...@redhat.com wrote: On Wed, 3 Feb 2016 11:47:56 +0100

RE: [patch net-next RFC 0/6] Introduce devlink interface and first drivers to use it

2016-02-04 Thread Rosen, Rami
Hi, >Btw, if you add this tool into iproute2 (which would be preferred), >then >probably dl should be ok (and easier retrievable in that relation). +1. This tool, which uses netlink messages, seems a natural candidate for iproute2. And also apart from "ip", we have also another short command i

Re: [patch net-next RFC 0/6] Introduce devlink interface and first drivers to use it

2016-02-04 Thread Jiri Pirko
Thu, Feb 04, 2016 at 02:22:17PM CET, han...@stressinduktion.org wrote: >On 03.02.2016 16:17, Daniel Borkmann wrote: >>On 02/03/2016 02:33 PM, Jiri Pirko wrote: >>>Wed, Feb 03, 2016 at 02:31:33PM CET, bro...@redhat.com wrote: On Wed, 3 Feb 2016 11:47:56 +0100 Jiri Pirko wrote: >From: J

Re: [patch net-next RFC 0/6] Introduce devlink interface and first drivers to use it

2016-02-04 Thread Hannes Frederic Sowa
On 03.02.2016 16:17, Daniel Borkmann wrote: On 02/03/2016 02:33 PM, Jiri Pirko wrote: Wed, Feb 03, 2016 at 02:31:33PM CET, bro...@redhat.com wrote: On Wed, 3 Feb 2016 11:47:56 +0100 Jiri Pirko wrote: From: Jiri Pirko [...] It is available here: https://github.com/jpirko/devlink IHMO thi

Re: [patch net-next RFC 0/6] Introduce devlink interface and first drivers to use it

2016-02-03 Thread Daniel Borkmann
On 02/03/2016 02:33 PM, Jiri Pirko wrote: Wed, Feb 03, 2016 at 02:31:33PM CET, bro...@redhat.com wrote: On Wed, 3 Feb 2016 11:47:56 +0100 Jiri Pirko wrote: From: Jiri Pirko [...] It is available here: https://github.com/jpirko/devlink IHMO this very short command name "dl" is not an adva

Re: [patch net-next RFC 0/6] Introduce devlink interface and first drivers to use it

2016-02-03 Thread Jiri Pirko
Wed, Feb 03, 2016 at 02:31:33PM CET, bro...@redhat.com wrote: >On Wed, 3 Feb 2016 11:47:56 +0100 >Jiri Pirko wrote: > >> From: Jiri Pirko >> >> There a is need for some userspace API that would allow to expose things >> that are not directly related to any device class like net_device of >> ib_

Re: [patch net-next RFC 0/6] Introduce devlink interface and first drivers to use it

2016-02-03 Thread Jesper Dangaard Brouer
On Wed, 3 Feb 2016 11:47:56 +0100 Jiri Pirko wrote: > From: Jiri Pirko > > There a is need for some userspace API that would allow to expose things > that are not directly related to any device class like net_device of > ib_device, but rather chip-wide/switch-ASIC-wide stuff. > > Use cases: >