Searched hist:"63561 a403c7c89d59205401db14fb444c6535cef" (Results 1 – 2 of 2) sorted by relevance
| /openbmc/linux/net/mptcp/ |
| H A D | subflow.c | diff 63561a403c7c89d59205401db14fb444c6535cef Mon Sep 14 03:01:07 CDT 2020 Paolo Abeni <pabeni@redhat.com> mptcp: rethink 'is writable' conditional
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 <pabeni@redhat.com>
Reviewed-by: Mat Martineau <mathew.j.martineau@linux.intel.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
|
| H A D | protocol.c | diff 63561a403c7c89d59205401db14fb444c6535cef Mon Sep 14 03:01:07 CDT 2020 Paolo Abeni <pabeni@redhat.com> mptcp: rethink 'is writable' conditional
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 <pabeni@redhat.com>
Reviewed-by: Mat Martineau <mathew.j.martineau@linux.intel.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
|