Re: [PATCH net-next v4 09/12] bridge: mrp: Extend MRP netlink interface for configuring MRP interconnect

2020-07-14 Thread Nikolay Aleksandrov
On 14/07/2020 10:34, Horatiu Vultur wrote: > This patch extends the existing MRP netlink interface with the following > attributes: IFLA_BRIDGE_MRP_IN_ROLE, IFLA_BRIDGE_MRP_IN_STATE and > IFLA_BRIDGE_MRP_START_IN_TEST. These attributes are similar with their > ring attributes but they

[PATCH net-next v4 09/12] bridge: mrp: Extend MRP netlink interface for configuring MRP interconnect

2020-07-14 Thread Horatiu Vultur
This patch extends the existing MRP netlink interface with the following attributes: IFLA_BRIDGE_MRP_IN_ROLE, IFLA_BRIDGE_MRP_IN_STATE and IFLA_BRIDGE_MRP_START_IN_TEST. These attributes are similar with their ring attributes but they apply to the interconnect port. Signed-off-by: Horatiu Vultur

[PATCH net-next v3 09/12] bridge: mrp: Extend MRP netlink interface for configuring MRP interconnect

2020-07-12 Thread Horatiu Vultur
This patch extends the existing MRP netlink interface with the following attributes: IFLA_BRIDGE_MRP_IN_ROLE, IFLA_BRIDGE_MRP_IN_STATE and IFLA_BRIDGE_MRP_START_IN_TEST. These attributes are similar with their ring attributes but they apply to the interconnect port. Signed-off-by: Horatiu Vultur

[PATCH net-next v2 09/12] bridge: mrp: Extend MRP netlink interface for configuring MRP interconnect

2020-07-09 Thread Horatiu Vultur
This patch extends the existing MRP netlink interface with the following attributes: IFLA_BRIDGE_MRP_IN_ROLE, IFLA_BRIDGE_MRP_IN_STATE and IFLA_BRIDGE_MRP_START_IN_TEST. These attributes are similar with their ring attributes but they apply to the interconnect port. Signed-off-by: Horatiu Vultur

[PATCH net-next 09/12] bridge: mrp: Extend MRP netlink interface for configuring MRP interconnect

2020-07-06 Thread Horatiu Vultur
This patch extends the existing MRP netlink interface with the following attributes: IFLA_BRIDGE_MRP_IN_ROLE, IFLA_BRIDGE_MRP_IN_STATE and IFLA_BRIDGE_MRP_START_IN_TEST. These attributes are similar with their ring attributes but they apply to the interconnect port. Signed-off-by: Horatiu Vultur

Re: [PATCH net-next v3 0/2] bridge: mrp: Extend MRP netlink interface with IFLA_BRIDGE_MRP_CLEAR

2020-06-28 Thread Horatiu Vultur
The 06/26/2020 13:00, David Miller wrote: > EXTERNAL EMAIL: Do not click links or open attachments unless you know the > content is safe > > From: Horatiu Vultur > Date: Fri, 26 Jun 2020 09:33:47 +0200 > > > This patch series extends MRP netlink interface with IFLA_

Re: [PATCH net-next v3 0/2] bridge: mrp: Extend MRP netlink interface with IFLA_BRIDGE_MRP_CLEAR

2020-06-26 Thread David Miller
From: Horatiu Vultur Date: Fri, 26 Jun 2020 09:33:47 +0200 > This patch series extends MRP netlink interface with IFLA_BRIDGE_MRP_CLEAR. > To allow the userspace to clear all MRP instances when is started. The > second patch in the series fix different sparse warnings. > > v3

[PATCH net-next v3 0/2] bridge: mrp: Extend MRP netlink interface with IFLA_BRIDGE_MRP_CLEAR

2020-06-26 Thread Horatiu Vultur
This patch series extends MRP netlink interface with IFLA_BRIDGE_MRP_CLEAR. To allow the userspace to clear all MRP instances when is started. The second patch in the series fix different sparse warnings. v3: - add the second patch to fix sparse warnings v2: - use list_for_each_entry_safe

[PATCH net-next v3 1/2] bridge: mrp: Extend MRP netlink interface with IFLA_BRIDGE_MRP_CLEAR

2020-06-26 Thread Horatiu Vultur
In case the userspace daemon dies, then when is restarted it doesn't know if there are any MRP instances in the kernel. Therefore extend the netlink interface to allow the daemon to clear all MRP instances when is started. Signed-off-by: Horatiu Vultur --- include/uapi/linux/if_bridge.h | 8 +++

Re: [PATCH net-next v2] bridge: mrp: Extend MRP netlink interface with IFLA_BRIDGE_MRP_CLEAR

2020-06-25 Thread Horatiu Vultur
e sparse warnings. I will move this patch in a patch series where I will fix also these warnings. > > > [auto build test WARNING on net-next/master] > > > > url: > > https://github.com/0day-ci/linux/commits/Horatiu-Vultur/bridge-mrp-Extend-MRP-netlink-interface-with

Re: [PATCH net-next v2] bridge: mrp: Extend MRP netlink interface with IFLA_BRIDGE_MRP_CLEAR

2020-06-25 Thread Nikolay Aleksandrov
ik > [auto build test WARNING on net-next/master] > > url: > https://github.com/0day-ci/linux/commits/Horatiu-Vultur/bridge-mrp-Extend-MRP-netlink-interface-with-IFLA_BRIDGE_MRP_CLEAR/20200625-150941 > base: https://git.kernel.org/pub/sc

Re: [PATCH net-next v2] bridge: mrp: Extend MRP netlink interface with IFLA_BRIDGE_MRP_CLEAR

2020-06-25 Thread kernel test robot
Hi Horatiu, Thank you for the patch! Perhaps something to improve: [auto build test WARNING on net-next/master] url: https://github.com/0day-ci/linux/commits/Horatiu-Vultur/bridge-mrp-Extend-MRP-netlink-interface-with-IFLA_BRIDGE_MRP_CLEAR/20200625-150941 base: https://git.kernel.org/pub

[PATCH net-next v2] bridge: mrp: Extend MRP netlink interface with IFLA_BRIDGE_MRP_CLEAR

2020-06-25 Thread Horatiu Vultur
In case the userspace daemon dies, then when is restarted it doesn't know if there are any MRP instances in the kernel. Therefore extend the netlink interface to allow the daemon to clear all MRP instances when is started. Signed-off-by: Horatiu Vultur --- v2: - use list_for_each_entry_safe in

Re: [PATCH net-next] bridge: mrp: Extend MRP netlink interface with IFLA_BRIDGE_MRP_CLEAR

2020-06-24 Thread Horatiu Vultur
The 06/24/2020 11:19, Nikolay Aleksandrov wrote: > EXTERNAL EMAIL: Do not click links or open attachments unless you know the > content is safe > > On 24/06/2020 11:05, Horatiu Vultur wrote: > > In case the userspace daemon dies, then when is restarted it doesn't > > know if there are any MRP ins

[PATCH net-next] bridge: mrp: Extend MRP netlink interface with IFLA_BRIDGE_MRP_CLEAR

2020-06-24 Thread Horatiu Vultur
In case the userspace daemon dies, then when is restarted it doesn't know if there are any MRP instances in the kernel. Therefore extend the netlink interface to allow the daemon to clear all MRP instances when is started. Signed-off-by: Horatiu Vultur --- include/uapi/linux/if_bridge.h | 8 +++

Re: [PATCH net-next] bridge: mrp: Extend MRP netlink interface with IFLA_BRIDGE_MRP_CLEAR

2020-06-24 Thread Nikolay Aleksandrov
On 24/06/2020 11:05, Horatiu Vultur wrote: > In case the userspace daemon dies, then when is restarted it doesn't > know if there are any MRP instances in the kernel. Therefore extend the > netlink interface to allow the daemon to clear all MRP instances when is > started. > > Signed-off-by: Horat

Re: [PATCH net-next v2] bridge: mrp: Rework the MRP netlink interface

2020-05-27 Thread David Miller
From: Horatiu Vultur Date: Wed, 27 May 2020 12:34:30 + > This patch reworks the MRP netlink interface. Before, each attribute > represented a binary structure which made it hard to be extended. > Therefore update the MRP netlink interface such that each existing > attribute to

Re: [PATCH net-next v2] bridge: mrp: Rework the MRP netlink interface

2020-05-27 Thread Nikolay Aleksandrov
On 27/05/2020 15:34, Horatiu Vultur wrote: > This patch reworks the MRP netlink interface. Before, each attribute > represented a binary structure which made it hard to be extended. > Therefore update the MRP netlink interface such that each existing > attribute to be a nested att

[PATCH net-next v2] bridge: mrp: Rework the MRP netlink interface

2020-05-27 Thread Horatiu Vultur
This patch reworks the MRP netlink interface. Before, each attribute represented a binary structure which made it hard to be extended. Therefore update the MRP netlink interface such that each existing attribute to be a nested attribute which contains the fields of the binary structures. In this

Re: [PATCH net-next] bridge: mrp: Rework the MRP netlink interface

2020-05-27 Thread Horatiu Vultur
The 05/27/2020 11:59, Nikolay Aleksandrov wrote: > EXTERNAL EMAIL: Do not click links or open attachments unless you know the > content is safe > > On 26/05/2020 17:22, Horatiu Vultur wrote: > > This patch rework the MRP netlink interface. Before, each attribute > &

Re: [PATCH net-next] bridge: mrp: Rework the MRP netlink interface

2020-05-27 Thread Nikolay Aleksandrov
On 26/05/2020 17:22, Horatiu Vultur wrote: > This patch rework the MRP netlink interface. Before, each attribute > represented a binary structure which made it hard to be extended. > Therefore update the MRP netlink interface such that each existing > attribute to be a nested att

[PATCH net-next] bridge: mrp: Rework the MRP netlink interface

2020-05-26 Thread Horatiu Vultur
This patch rework the MRP netlink interface. Before, each attribute represented a binary structure which made it hard to be extended. Therefore update the MRP netlink interface such that each existing attribute to be a nested attribute which contains the fields of the binary structures. In this

Re: MRP netlink interface

2020-05-25 Thread Michal Kubecek
showing why passing data > > > structures as binary data via netlink is a bad idea. I definitely > > > wouldn't advice this approach for any new interface. One of the > > > strengths of netlink is the ability to use structured and extensible > > > mess

Re: MRP netlink interface

2020-05-25 Thread Horatiu Vultur
is approach for any new interface. One of the > > strengths of netlink is the ability to use structured and extensible > > messages. > > > >> Another approach is to restructure MRP netlink interface. What I was > >> thinking to > >> keep the current attributes

Re: MRP netlink interface

2020-05-25 Thread Nikolay Aleksandrov
netlink is a bad idea. I definitely > wouldn't advice this approach for any new interface. One of the > strengths of netlink is the ability to use structured and extensible > messages. > >> Another approach is to restructure MRP netlink interface. What I was >> thinkin

Re: MRP netlink interface

2020-05-25 Thread Michal Kubecek
he strengths of netlink is the ability to use structured and extensible messages. > Another approach is to restructure MRP netlink interface. What I was thinking > to > keep the current attributes (IFLA_BRIDGE_MRP_INSTANCE, > IFLA_BRIDGE_MRP_PORT_STATE,...) but they will be nested attr

Re: MRP netlink interface

2020-05-25 Thread Horatiu Vultur
by the priority of each node. So > > to have this functionality I have to extend the MRP netlink interface > > and this brings me to my issues. > > > > My first approach was to extend the 'struct br_mrp_instance' with a field > > that > > contains th

Re: MRP netlink interface

2020-05-25 Thread Nikolay Aleksandrov
h MRA role can behave as a MRM(Manager) or as a > MRC(Client). The behaviour is decided by the priority of each node. So > to have this functionality I have to extend the MRP netlink interface > and this brings me to my issues. > > My first approach was to extend the 'struct br_m

MRP netlink interface

2020-05-25 Thread Horatiu Vultur
decided by the priority of each node. So to have this functionality I have to extend the MRP netlink interface and this brings me to my issues. My first approach was to extend the 'struct br_mrp_instance' with a field that contains the priority of the node. But this breaks the