All of lore.kernel.org
 help / color / mirror / Atom feed
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 v19 0/9] BPF redundant scheduler, part 1
Date: Tue, 15 Nov 2022 16:41:15 -0800 (PST)	[thread overview]
Message-ID: <76ad0b0b-e55c-22cc-690f-c0fcdd78fca6@linux.intel.com> (raw)
In-Reply-To: <cover.1668151131.git.geliang.tang@suse.com>

On Fri, 11 Nov 2022, Geliang Tang wrote:

> v19:
> - update patch 1.
> - split "BPF redundant scheduler" into two parts.
> - rebased on "export/20221111T055536".
>

Thanks Geliang.

I think v19 (part 1) looks ok for the export branch. simult_flows.sh was 
slightly faster (small sample size :) ) on my VM, for what it's worth.

Looks like the first three patches go at the beginning of the "features 
net-next-next" section, correct?

Reviewed-by: Mat Martineau <mathew.j.martineau@linux.intel.com>

> Geliang Tang (9):
>  mptcp: refactor push_pending logic
>  mptcp: drop last_snd and MPTCP_RESET_SCHEDULER
>  mptcp: add sched_data_set_contexts helper
>  Squash to "mptcp: add struct mptcp_sched_ops"
>  Squash to "bpf: Add bpf_mptcp_sched_ops"
>  Squash to "bpf: Add bpf_mptcp_sched_kfunc_set"
>  Squash to "selftests/bpf: Add bpf_first scheduler"
>  Squash to "selftests/bpf: Add bpf_bkup scheduler"
>  Squash to "selftests/bpf: Add bpf_rr scheduler"
>
> include/net/mptcp.h                           |   6 +-
> net/mptcp/bpf.c                               |   1 +
> net/mptcp/pm.c                                |   9 +-
> net/mptcp/pm_netlink.c                        |   3 -
> net/mptcp/protocol.c                          | 161 +++++++++---------
> net/mptcp/protocol.h                          |   1 -
> net/mptcp/sched.c                             |  21 ++-
> tools/testing/selftests/bpf/bpf_tcp_helpers.h |   8 +-
> .../selftests/bpf/progs/mptcp_bpf_bkup.c      |  10 +-
> .../selftests/bpf/progs/mptcp_bpf_first.c     |  10 +-
> .../selftests/bpf/progs/mptcp_bpf_rr.c        |  10 +-
> 11 files changed, 143 insertions(+), 97 deletions(-)
>
> -- 
> 2.35.3
>
>
>

--
Mat Martineau
Intel

  parent reply	other threads:[~2022-11-16  0:41 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-11  7:47 [PATCH mptcp-next v19 0/9] BPF redundant scheduler, part 1 Geliang Tang
2022-11-11  7:47 ` [PATCH mptcp-next v19 1/9] mptcp: refactor push_pending logic Geliang Tang
2022-11-11  7:47 ` [PATCH mptcp-next v19 2/9] mptcp: drop last_snd and MPTCP_RESET_SCHEDULER Geliang Tang
2022-11-11  7:47 ` [PATCH mptcp-next v19 3/9] mptcp: add sched_data_set_contexts helper Geliang Tang
2022-11-18 18:10   ` Matthieu Baerts
2022-11-18 18:26     ` Mat Martineau
2022-11-18 22:15       ` Geliang Tang
2022-11-11  7:47 ` [PATCH mptcp-next v19 4/9] Squash to "mptcp: add struct mptcp_sched_ops" Geliang Tang
2022-11-11  7:48 ` [PATCH mptcp-next v19 5/9] Squash to "bpf: Add bpf_mptcp_sched_ops" Geliang Tang
2022-11-11  7:48 ` [PATCH mptcp-next v19 6/9] Squash to "bpf: Add bpf_mptcp_sched_kfunc_set" Geliang Tang
2022-11-11  7:48 ` [PATCH mptcp-next v19 7/9] Squash to "selftests/bpf: Add bpf_first scheduler" Geliang Tang
2022-11-11  7:48 ` [PATCH mptcp-next v19 8/9] Squash to "selftests/bpf: Add bpf_bkup scheduler" Geliang Tang
2022-11-11  7:48 ` [PATCH mptcp-next v19 9/9] Squash to "selftests/bpf: Add bpf_rr scheduler" Geliang Tang
2022-11-11  8:12   ` Squash to "selftests/bpf: Add bpf_rr scheduler": Build Failure MPTCP CI
2022-11-11  9:53   ` Squash to "selftests/bpf: Add bpf_rr scheduler": Tests Results MPTCP CI
2022-11-16  1:01   ` Squash to "selftests/bpf: Add bpf_rr scheduler": Build Failure MPTCP CI
2022-11-16  2:38   ` Squash to "selftests/bpf: Add bpf_rr scheduler": Tests Results MPTCP CI
2022-11-16  0:41 ` Mat Martineau [this message]
2022-11-16  2:17   ` [PATCH mptcp-next v19 0/9] BPF redundant scheduler, part 1 Geliang Tang
2022-11-18 14:52 ` Matthieu Baerts
2022-11-18 15:12   ` Geliang Tang
2022-12-09  3:18   ` Geliang Tang
2022-12-14 17:34     ` Matthieu Baerts

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=76ad0b0b-e55c-22cc-690f-c0fcdd78fca6@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 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.