Messages in this thread | | | From | Jürgen Lambrecht <> | Subject | Re: [RFC net-next v3 06/10] net: bridge: mrp: switchdev: Extend switchdev API to offload MRP | Date | Tue, 28 Jan 2020 10:50:34 +0100 |
| |
[sending again to vger.kernel.org, because previous was rejected]
On 1/27/20 12:04 PM, Allan W. Nielsen wrote: >>> > How do you handle the 'headless chicken' scenario? User space tells >>> > the port to start sending MRP_Test frames. It then dies. The hardware
Andrew, I am a bit confused here - maybe I missed an email-thread, I'm sorry then.
In previous emails you and others talked about hardware support to send packets (inside the switch). But somebody also talked about data-plane and control-plane (about STP in-kernel being a bad idea), and that data-plane is in-kernel, and control plane is a mrp-daemon (in user space). And in my mind, the "hardware" you mention is a frame-injector and can be both real hardware and a driver in the kernel.
Do I see it right?
>>> > continues sending these messages, and the neighbours thinks everything >>> > is O.K, but in reality the state machine is dead, and when the ring >>> > breaks, the daemon is not there to fix it? > I agree, we need to find a solution to this issue. >
| |