MPTCP Linux Development
 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 00/10] register default scheduler
Date: Tue, 11 Oct 2022 15:32:34 -0700 (PDT)	[thread overview]
Message-ID: <0d086d85-29c6-a903-344b-6ab6ae0c62a0@linux.intel.com> (raw)
In-Reply-To: <cover.1665154582.git.geliang.tang@suse.com>

On Fri, 7 Oct 2022, Geliang Tang wrote:

> Register the burst scheduler as the default one.
>
> - depends on "refactor push pending" v5
>

Hi Geliang -

I couldn't get these to apply on v5 or v6 of the other series, I also 
tried using older export tags. But I think there are some issues to work 
on with "refactor push pending", so it might be best to get that series 
settled before rebasing and reposting this.

- Mat

> Geliang Tang (10):
>  Squash to "mptcp: add struct mptcp_sched_ops"
>  Squash to "mptcp: add get_subflow wrappers" II
>  mptcp: add mptcp_sched_data_set_contexts helper
>  mptcp: add mptcp_sched_data argument
>  mptcp: register default scheduler
>  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                           |  7 +-
> net/mptcp/bpf.c                               |  1 +
> net/mptcp/protocol.c                          | 33 ++++---
> net/mptcp/protocol.h                          | 13 ++-
> net/mptcp/sched.c                             | 91 ++++++++++---------
> tools/testing/selftests/bpf/bpf_tcp_helpers.h |  9 +-
> .../selftests/bpf/progs/mptcp_bpf_bkup.c      | 10 +-
> .../selftests/bpf/progs/mptcp_bpf_first.c     | 10 +-
> .../selftests/bpf/progs/mptcp_bpf_rr.c        | 10 +-
> 9 files changed, 116 insertions(+), 68 deletions(-)
>
> -- 
> 2.35.3
>
>
>

--
Mat Martineau
Intel

      parent reply	other threads:[~2022-10-11 22:32 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-07 15:02 [PATCH mptcp-next 00/10] register default scheduler Geliang Tang
2022-10-07 15:02 ` [PATCH mptcp-next 01/10] Squash to "mptcp: add struct mptcp_sched_ops" Geliang Tang
2022-10-07 15:02 ` [PATCH mptcp-next 02/10] Squash to "mptcp: add get_subflow wrappers" II Geliang Tang
2022-10-07 15:02 ` [PATCH mptcp-next 03/10] mptcp: add mptcp_sched_data_set_contexts helper Geliang Tang
2022-10-07 15:02 ` [PATCH mptcp-next 04/10] mptcp: add mptcp_sched_data argument Geliang Tang
2022-10-07 15:02 ` [PATCH mptcp-next 05/10] mptcp: register default scheduler Geliang Tang
2022-10-07 15:02 ` [PATCH mptcp-next 06/10] Squash to "bpf: Add bpf_mptcp_sched_ops" Geliang Tang
2022-10-07 15:02 ` [PATCH mptcp-next 07/10] Squash to "bpf: Add bpf_mptcp_sched_kfunc_set" Geliang Tang
2022-10-07 15:02 ` [PATCH mptcp-next 08/10] Squash to "selftests/bpf: Add bpf_first scheduler" Geliang Tang
2022-10-07 15:02 ` [PATCH mptcp-next 09/10] Squash to "selftests/bpf: Add bpf_bkup scheduler" Geliang Tang
2022-10-07 15:02 ` [PATCH mptcp-next 10/10] Squash to "selftests/bpf: Add bpf_rr scheduler" Geliang Tang
2022-10-11 22:32 ` Mat Martineau [this message]

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=0d086d85-29c6-a903-344b-6ab6ae0c62a0@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