From: Geliang Tang <geliang.tang@suse.com>
To: mptcp@lists.linux.dev
Cc: Geliang Tang <geliang.tang@suse.com>
Subject: [PATCH mptcp-next v7 00/12] refactor push pending
Date: Wed, 12 Oct 2022 12:39:55 +0800 [thread overview]
Message-ID: <cover.1665549148.git.geliang.tang@suse.com> (raw)
v7:
- update delegate sending in patch 10
- rebase to export/20221011T063543.
- This series should be merged between the commit "mptcp: add get_subflow
wrappers" and "bpf: Add bpf_mptcp_sched_ops", except the last squash-to
patch.
v6:
- drop all msk->last_snd, add last_snd variable instead in patch 13
- fix lock_sock issue in patch 3
- merge squash-to patches
v5:
- address Mat's comments in v4.
v4:
- update __mptcp_subflow_push_pending as Mat suggested.
- add more patches from "BPF redundant scheduler" series.
v3:
- add a cleanup patch.
- remove msk->last_snd in mptcp_subflow_get_send().
- add the loop that calls the scheduler again in __mptcp_push_pending().
v2:
- add snd_burst check in dfrags loop as Mat suggested.
Refactor __mptcp_push_pending() and __mptcp_subflow_push_pending() to
remove duplicate code and support redundant scheduler more easily in
__mptcp_subflow_push_pending().
Geliang Tang (12):
Squash to "mptcp: add get_subflow wrappers"
mptcp: change 'first' as a parameter
mptcp: refactor push_pending logic
mptcp: drop last_snd of struct mptcp_sock
mptcp: simplify push_pending
mptcp: multi subflows push_pending
mptcp: use msk instead of mptcp_sk
mptcp: refactor subflow_push_pending logic
mptcp: simplify subflow_push_pending
mptcp: multi subflows subflow_push_pending
mptcp: multi subflows retrans support
Squash to "selftests/bpf: Add bpf_rr scheduler"
net/mptcp/pm.c | 9 +-
net/mptcp/pm_netlink.c | 3 -
net/mptcp/protocol.c | 283 ++++++++++--------
net/mptcp/protocol.h | 6 +-
net/mptcp/sched.c | 61 ++--
tools/testing/selftests/bpf/bpf_tcp_helpers.h | 1 -
.../selftests/bpf/progs/mptcp_bpf_rr.c | 6 +-
7 files changed, 186 insertions(+), 183 deletions(-)
--
2.35.3
next reply other threads:[~2022-10-12 4:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-12 4:39 Geliang Tang [this message]
2022-10-12 4:39 ` [PATCH mptcp-next v7 01/12] Squash to "mptcp: add get_subflow wrappers" Geliang Tang
2022-10-12 4:39 ` [PATCH mptcp-next v7 02/12] mptcp: change 'first' as a parameter Geliang Tang
2022-10-12 4:39 ` [PATCH mptcp-next v7 03/12] mptcp: refactor push_pending logic Geliang Tang
2022-10-12 4:39 ` [PATCH mptcp-next v7 04/12] mptcp: drop last_snd of struct mptcp_sock Geliang Tang
2022-10-12 4:40 ` [PATCH mptcp-next v7 05/12] mptcp: simplify push_pending Geliang Tang
2022-10-12 4:40 ` [PATCH mptcp-next v7 06/12] mptcp: multi subflows push_pending Geliang Tang
2022-10-12 4:40 ` [PATCH mptcp-next v7 07/12] mptcp: use msk instead of mptcp_sk Geliang Tang
2022-10-12 4:40 ` [PATCH mptcp-next v7 08/12] mptcp: refactor subflow_push_pending logic Geliang Tang
2022-10-12 4:40 ` [PATCH mptcp-next v7 09/12] mptcp: simplify subflow_push_pending Geliang Tang
2022-10-12 4:40 ` [PATCH mptcp-next v7 10/12] mptcp: multi subflows subflow_push_pending Geliang Tang
2022-10-14 1:14 ` Mat Martineau
2022-10-12 4:40 ` [PATCH mptcp-next v7 11/12] mptcp: multi subflows retrans support Geliang Tang
2022-10-12 4:40 ` [PATCH mptcp-next v7 12/12] Squash to "selftests/bpf: Add bpf_rr scheduler" Geliang Tang
2022-10-12 6:08 ` Squash to "selftests/bpf: Add bpf_rr scheduler": Tests Results MPTCP CI
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cover.1665549148.git.geliang.tang@suse.com \
--to=geliang.tang@suse.com \
--cc=mptcp@lists.linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.