diff options
author | Paolo Abeni <pabeni@redhat.com> | 2023-10-23 23:44:38 +0300 |
---|---|---|
committer | Jakub Kicinski <kuba@kernel.org> | 2023-10-25 22:23:34 +0300 |
commit | 5684ab1a0effbfeb706f47d85785f653005b97b1 (patch) | |
tree | 545dd36c49a503cee46fc07f4e686801b3829d05 /drivers/nfc | |
parent | 849ee75a38b297187c760bb1d23d8f2a7b1fc73e (diff) | |
download | linux-5684ab1a0effbfeb706f47d85785f653005b97b1.tar.xz |
mptcp: give rcvlowat some love
The MPTCP protocol allow setting sk_rcvlowat, but the value there
is currently ignored.
Additionally, the default subflows sk_rcvlowat basically disables per
subflow delayed ack: the MPTCP protocol move the incoming data from the
subflows into the msk socket as soon as the TCP stacks invokes the subflow
data_ready callback. Later, when __tcp_ack_snd_check() takes action,
the subflow-level copied_seq matches rcv_nxt, and that mandate for an
immediate ack.
Let the mptcp receive path be aware of such threshold, explicitly tracking
the amount of data available to be ready and checking vs sk_rcvlowat in
mptcp_poll() and before waking-up readers.
Additionally implement the set_rcvlowat() callback, to properly handle
the rcvbuf auto-tuning on sk_rcvlowat changes.
Finally to properly handle delayed ack, force the subflow level threshold
to 0 and instead explicitly ask for an immediate ack when the msk level th
is not reached.
Reviewed-by: Mat Martineau <martineau@kernel.org>
Signed-off-by: Paolo Abeni <pabeni@redhat.com>
Signed-off-by: Mat Martineau <martineau@kernel.org>
Link: https://lore.kernel.org/r/20231023-send-net-next-20231023-2-v1-5-9dc60939d371@kernel.org
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'drivers/nfc')
0 files changed, 0 insertions, 0 deletions