in-kernel PM: use either subflow or signal depending on connector/listener app #590
Description
Pre-requisites
- A similar idea has not been reported before.
- mptcp.dev website does not cover my case.
- The wiki doesn't cover my case.
Description
It might be easier to configure the PM by setting both subflow and signal flags (and luminar?), but telling the PM to either create new subflow or signal new addresses depending on the socket type: connector vs listener.
Solution
We could have a new (per-netns) global option to set this mode or not.
Considered alternatives
Using different netns per application type, but that's not really practical.
Additional context
The idea comes from #587