mptcp_poll should not block on each subflow
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest3 patches 2 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/3 | mptcp: add and use subflow_write_spacenet/ | +11 | 0 replies | |
| 2/3 | net: tcp: add __tcp_poll helperinclude/ net/ | +9 | 0 replies | |
| 3/3 | mptcp: switch mptcp_poll to mptcp socket wait queuenet/ net/ net/ | +18 | 2 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [MPTCP] [PATCH mptcp-next 0/3] mptcp_poll should not block on each subflow
This is a (very simplified) version of the mptcp poll refactoring.
I've removed all of the code from mptcp_should_wake_parent(), the reason is that Paolo is working on moving more code from mptcp_recvmsg to the subflow data_ready callback so we can weed out duplicate data before waking up userspace.
So this only contains the new 'subflow_write_space' callback to notify mptcp layer when a subflow isn't blocked anymore on write-side, plus the __tcp_poll split so we can call the tcp layer from mptcp without placing the subflow socket on a wait list.
Comments welcome.