[PATCH v11 mptcp-next 0/2] mptcp: address stall under memory pressure

Paolo Abeni posted 2 patches 1 week, 1 day ago
Patches applied successfully (tree, apply log)
git fetch https://github.com/multipath-tcp/mptcp_net-next tags/patchew/cover.1780152380.git.pabeni@redhat.com
There is a newer version of this series
net/mptcp/protocol.c | 156 +++++++++++++++++++++++++++++++------------
1 file changed, 112 insertions(+), 44 deletions(-)
[PATCH v11 mptcp-next 0/2] mptcp: address stall under memory pressure
Posted by Paolo Abeni 1 week, 1 day ago
This brings (hopefully) the final bits required to address the
data transfer stall reported by Geliang and Gang 

This series improves mptcp retranmission to make them reliable:
pruning can require some of them.

The only change over the previous iteration is in patch 2, addressing
Geliang and sashiko feedback over the previous iteration (bad WARN
condition).

Paolo Abeni (2):
  mptcp: move the retrans loop to a separate helper
  mptcp: let the retrans scheduler do its job.

 net/mptcp/protocol.c | 156 +++++++++++++++++++++++++++++++------------
 1 file changed, 112 insertions(+), 44 deletions(-)

-- 
2.54.0
Re: [PATCH v11 mptcp-next 0/2] mptcp: address stall under memory pressure
Posted by MPTCP CI 1 week, 1 day ago
Hi Paolo,

Thank you for your modifications, that's great!

Our CI did some validations and here is its report:

- KVM Validation: normal (except selftest_mptcp_join): Success! ✅
- KVM Validation: normal (only selftest_mptcp_join): Success! ✅
- KVM Validation: debug (except selftest_mptcp_join): Success! ✅
- KVM Validation: debug (only selftest_mptcp_join): Success! ✅
- KVM Validation: btf-normal (only bpftest_all): Success! ✅
- KVM Validation: btf-debug (only bpftest_all): Success! ✅
- Task: https://github.com/multipath-tcp/mptcp_net-next/actions/runs/26687469839

Initiator: Patchew Applier
Commits: https://github.com/multipath-tcp/mptcp_net-next/commits/89eb2ec6592a
Patchwork: https://patchwork.kernel.org/project/mptcp/list/?series=1103334


If there are some issues, you can reproduce them using the same environment as
the one used by the CI thanks to a docker image, e.g.:

    $ cd [kernel source code]
    $ docker run -v "${PWD}:${PWD}:rw" -w "${PWD}" --privileged --rm -it \
        --pull always mptcp/mptcp-upstream-virtme-docker:latest \
        auto-normal

For more details:

    https://github.com/multipath-tcp/mptcp-upstream-virtme-docker


Please note that despite all the efforts that have been already done to have a
stable tests suite when executed on a public CI like here, it is possible some
reported issues are not due to your modifications. Still, do not hesitate to
help us improve that ;-)

Cheers,
MPTCP GH Action bot
Bot operated by Matthieu Baerts (NGI0 Core)