All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthieu Baerts <matthieu.baerts@tessares.net>
To: Geliang Tang <geliang.tang@suse.com>, mptcp@lists.linux.dev
Subject: Re: [PATCH mptcp-next v18 0/7] BPF packet scheduler
Date: Tue, 3 May 2022 18:28:55 +0200	[thread overview]
Message-ID: <00bc1734-033a-cb99-08ee-654b35a2400b@tessares.net> (raw)
In-Reply-To: <cover.1651412613.git.geliang.tang@suse.com>

Hi Geliang, Mat, Paolo,

On 01/05/2022 15:48, Geliang Tang wrote:
> v18:
>  - drop "mptcp: add last_snd write access".
>  - add mptcp_sched_data_init helper.
>  - move mptcp_sched_get_send() and mptcp_sched_get_retrans() into sched.c.

Thank you for the patches and reviews!

Now in our tree (feat. for others) with Paolo's ACK and Mat's RvB tags:

New patches for t/upstream:
- 2d934cabfc25: mptcp: add struct mptcp_sched_ops
- 467bf7c54c40: mptcp: add a new sysctl scheduler
- 9281e21f5f4d: mptcp: add sched in mptcp_sock
- 656ddb9db4e1: mptcp: add get_subflow wrappers
- be9de4168364: mptcp: add bpf_mptcp_sched_ops
- 2885b934b680: selftests: bpf: add bpf_first scheduler
- 0201204572f8: selftests: bpf: add bpf_first test
- Results: bea7cea0ffcd..9d8bf95bd8a7 (export)

And the squash-to patches:

- d8a1213416ef: "squashed" in "mptcp: add get_subflow wrappers"
- Results: 9d8bf95bd8a7..4c418cbad090 (export)

- 014d79843c44: "squashed" in "mptcp: add bpf_mptcp_sched_ops"
- Results: 4c418cbad090..aa6bec3f788f (export)

- 3b8d5a354bf6: "squashed" in "mptcp: add struct mptcp_sched_ops"
- Results: aa6bec3f788f..527315ca1901 (export)

- 92b309479c5c: "squashed" in "selftests: bpf: add bpf_first scheduler"
- Results: 527315ca1901..a800c43a02ab (export)

- 35a824bb888a: "squashed" in "selftests: bpf: add bpf_first test"
- Results: a800c43a02ab..c3f5d94e8dc4 (export)


Builds and tests are now in progress:

https://cirrus-ci.com/github/multipath-tcp/mptcp_net-next/export/20220503T162811
https://github.com/multipath-tcp/mptcp_net-next/actions/workflows/build-validation.yml?query=branch:export


> Closes: https://github.com/multipath-tcp/mptcp_net-next/issues/75

I didn't close it because "BPF round-robin scheduler" series also closes it.

Cheers,
Matt
-- 
Tessares | Belgium | Hybrid Access Solutions
www.tessares.net

      parent reply	other threads:[~2022-05-03 16:28 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-01 13:48 [PATCH mptcp-next v18 0/7] BPF packet scheduler Geliang Tang
2022-05-01 13:48 ` [PATCH mptcp-next v18 1/7] mptcp: add struct mptcp_sched_ops Geliang Tang
2022-05-01 13:48 ` [PATCH mptcp-next v18 2/7] mptcp: add a new sysctl scheduler Geliang Tang
2022-05-01 13:48 ` [PATCH mptcp-next v18 3/7] mptcp: add sched in mptcp_sock Geliang Tang
2022-05-01 13:48 ` [PATCH mptcp-next v18 4/7] mptcp: add get_subflow wrappers Geliang Tang
2022-05-01 13:48 ` [PATCH mptcp-next v18 5/7] mptcp: add bpf_mptcp_sched_ops Geliang Tang
2022-05-02 14:09   ` Paolo Abeni
2022-05-03  0:08     ` Mat Martineau
2022-05-01 13:48 ` [PATCH mptcp-next v18 6/7] selftests: bpf: add bpf_first scheduler Geliang Tang
2022-05-01 13:48 ` [PATCH mptcp-next v18 7/7] selftests: bpf: add bpf_first test Geliang Tang
2022-05-01 14:12   ` selftests: bpf: add bpf_first test: Build Failure MPTCP CI
2022-05-01 15:37   ` selftests: bpf: add bpf_first test: Tests Results MPTCP CI
2022-05-03 16:28 ` Matthieu Baerts [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=00bc1734-033a-cb99-08ee-654b35a2400b@tessares.net \
    --to=matthieu.baerts@tessares.net \
    --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.