MPTCP Linux Development
 help / color / mirror / Atom feed
From: Geliang Tang <geliang.tang@suse.com>
To: mptcp@lists.linux.dev
Cc: Geliang Tang <geliang.tang@suse.com>
Subject: [PATCH mptcp-next v3 0/5] refactor push pending
Date: Fri, 30 Sep 2022 22:17:30 +0800	[thread overview]
Message-ID: <cover.1664547250.git.geliang.tang@suse.com> (raw)

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 (5):
  mptcp: use msk instead of mptcp_sk(sk)
  mptcp: update __mptcp_push_pending
  mptcp: add do_push_pending helper
  mptcp: update __mptcp_subflow_push_pending
  mptcp: simplify __mptcp_subflow_push_pending

 net/mptcp/protocol.c | 162 ++++++++++++++++---------------------------
 1 file changed, 58 insertions(+), 104 deletions(-)

-- 
2.35.3


             reply	other threads:[~2022-09-30 14:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-30 14:17 Geliang Tang [this message]
2022-09-30 14:17 ` [PATCH mptcp-next v3 1/5] mptcp: use msk instead of mptcp_sk(sk) Geliang Tang
2022-09-30 14:17 ` [PATCH mptcp-next v3 2/5] mptcp: update __mptcp_push_pending Geliang Tang
2022-09-30 14:17 ` [PATCH mptcp-next v3 3/5] mptcp: add do_push_pending helper Geliang Tang
2022-09-30 14:17 ` [PATCH mptcp-next v3 4/5] mptcp: update __mptcp_subflow_push_pending Geliang Tang
2022-10-01  0:16   ` Mat Martineau
2022-09-30 14:17 ` [PATCH mptcp-next v3 5/5] mptcp: simplify __mptcp_subflow_push_pending Geliang Tang
2022-10-06 17:31   ` mptcp: simplify __mptcp_subflow_push_pending: 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.1664547250.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox