On Mon, 14 Sep 2020, Paolo Abeni wrote:
Currently, when checking for the 'msk is writable' condition, we
look at the individual subflows write space.
That works well while we send data via a single subflow, but will
not as soon as we will enable concurrent xmit on multiple subflows.
With this change msk becomes writable when the following conditions
hold:
- the socket has some free write space
- there is at least a subflow with write free space
Additionally we need to set the NOSPACE bit on all subflows
before blocking.
Signed-off-by: Paolo Abeni <pab...@redhat.com>
---
net/mptcp/protocol.c | 71 ++++++++++++++++++++++++++++----------------
net/mptcp/subflow.c | 6 ++--
2 files changed, 50 insertions(+), 27 deletions(-)
Thanks for the v2 Paolo. I've reviewed the series and will tag them all
so patchwork is updated.
Reviewed-by: Mat Martineau <mathew.j.martin...@linux.intel.com>
--
Mat Martineau
Intel
