From: Mat Martineau <mathew.j.martineau@linux.intel.com>
To: Geliang Tang <geliang.tang@suse.com>
Cc: mptcp@lists.linux.dev
Subject: Re: [PATCH mptcp-next v5 00/11] refactor push pending
Date: Thu, 6 Oct 2022 17:16:55 -0700 (PDT) [thread overview]
Message-ID: <86e6c9a8-4361-ec40-56ee-98c270d8342a@linux.intel.com> (raw)
In-Reply-To: <cover.1665058388.git.geliang.tang@suse.com>
On Thu, 6 Oct 2022, Geliang Tang wrote:
> v5:
> - address Mat's comments in v4.
Hi Geliang -
Thanks for the v5. I haven't finished looking over all the patches in
detail yet, but two things I do want to reply to right now:
* Thanks for explaining in patch 4 that last_snd is still useful for
round robin. I had forgotten about that, and it looked like a "write-only"
variable in the kernel code.
* In the meeting today Paolo suggested that a good test for the new
scheduler loop would be to modify simult_flows.sh to use much larger
files, then see if the modified code slowed down any of the simult_flows
tests.
He suggested making the test file 10x larger in simult_flows.sh:
- size=$((2 * 2048 * 4096))
+ size=$((2 * 2048 * 4096 * 10))
Can you compare the test times between the export branch and this series,
with both of them using the larger file size?
Thanks,
Mat
>
> 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 (11):
> Squash to "mptcp: add get_subflow wrappers"
> mptcp: 'first' argument for subflow_push_pending
> mptcp: refactor push_pending logic
> mptcp: drop last_snd for burst scheduler
> 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
>
> net/mptcp/pm.c | 9 +-
> net/mptcp/pm_netlink.c | 3 -
> net/mptcp/protocol.c | 285 ++++++++++++++++++++++-------------------
> net/mptcp/protocol.h | 5 +-
> net/mptcp/sched.c | 61 +++++----
> 5 files changed, 184 insertions(+), 179 deletions(-)
>
> --
> 2.35.3
>
>
>
--
Mat Martineau
Intel
next prev parent reply other threads:[~2022-10-07 0:17 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-06 12:17 [PATCH mptcp-next v5 00/11] refactor push pending Geliang Tang
2022-10-06 12:17 ` [PATCH mptcp-next v5 01/11] Squash to "mptcp: add get_subflow wrappers" Geliang Tang
2022-10-06 12:17 ` [PATCH mptcp-next v5 02/11] mptcp: 'first' argument for subflow_push_pending Geliang Tang
2022-10-06 12:17 ` [PATCH mptcp-next v5 03/11] mptcp: refactor push_pending logic Geliang Tang
2022-10-11 0:38 ` Mat Martineau
2022-10-06 12:17 ` [PATCH mptcp-next v5 04/11] mptcp: drop last_snd for burst scheduler Geliang Tang
2022-10-06 12:17 ` [PATCH mptcp-next v5 05/11] mptcp: simplify push_pending Geliang Tang
2022-10-06 12:17 ` [PATCH mptcp-next v5 06/11] mptcp: multi subflows push_pending Geliang Tang
2022-10-06 12:17 ` [PATCH mptcp-next v5 07/11] mptcp: use msk instead of mptcp_sk Geliang Tang
2022-10-06 12:17 ` [PATCH mptcp-next v5 08/11] mptcp: refactor subflow_push_pending logic Geliang Tang
2022-10-06 12:17 ` [PATCH mptcp-next v5 09/11] mptcp: simplify subflow_push_pending Geliang Tang
2022-10-06 12:17 ` [PATCH mptcp-next v5 10/11] mptcp: multi subflows subflow_push_pending Geliang Tang
2022-10-06 12:17 ` [PATCH mptcp-next v5 11/11] mptcp: multi subflows retrans support Geliang Tang
2022-10-06 17:53 ` mptcp: multi subflows retrans support: Tests Results MPTCP CI
2022-10-07 0:16 ` Mat Martineau [this message]
2022-10-07 9:00 ` [PATCH mptcp-next v5 00/11] refactor push pending Geliang Tang
2022-10-10 15:05 ` Geliang Tang
2022-10-11 0:12 ` Mat Martineau
2022-10-11 1:01 ` Mat Martineau
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=86e6c9a8-4361-ec40-56ee-98c270d8342a@linux.intel.com \
--to=mathew.j.martineau@linux.intel.com \
--cc=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