From: Matthieu Baerts <matttbe@kernel.org>
To: Gregory Detal <gregory.detal@gmail.com>,
MPTCP Upstream <mptcp@lists.linux.dev>
Subject: Re: [PATCH mptcp-next 0/2] mptcp: fix net.mptcp.scheduler behavior
Date: Fri, 3 May 2024 18:45:51 +0200 [thread overview]
Message-ID: <fef27199-7ec3-4390-9a71-9e76e59bc692@kernel.org> (raw)
In-Reply-To: <20240430-sysctl_scheduler-v1-0-8187148850df@gmail.com>
Hi Gregory, Geliang, Mat,
On 30/04/2024 14:06, Gregory Detal wrote:
> The sysctl is accepting any input. This patchset ensures only
> existing scheduler can be set.
>
> Moreover, this adds an helper sysctl to list the available scheduler
> similarly to tcp_available_congestion_control.
>
> The first patch of the series is a fix for mptcp-net.
Thank you for the patches, the tests, and the review:
New patches for t/upstream-net and t/upstream:
- bc3eac499491: mptcp: only allow set existing scheduler for
net.mptcp.scheduler
- Results: 9df9126ccb3d..193bf8fbc31b (export-net)
- Results: c1f52bb3cea5..e83515296801 (export)
New patches for t/upstream:
- 660afb67d62f: mptcp: add net.mptcp.available_schedulers
- Results: e83515296801..022e39266b3c (export)
Tests are now in progress:
- export:
https://github.com/multipath-tcp/mptcp_net-next/commit/56030f9d3812071365435354c0eb5ffb3504e58a/checks
- export-net:
https://github.com/multipath-tcp/mptcp_net-next/commit/a6e18d675691b704ed8e61862efa61464ffbeeb7/checks
Cheers,
Matt
--
Sponsored by the NGI0 Core fund.
prev parent reply other threads:[~2024-05-03 16:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-30 12:06 [PATCH mptcp-next 0/2] mptcp: fix net.mptcp.scheduler behavior Gregory Detal
2024-04-30 12:06 ` [PATCH mptcp-next 1/2] mptcp: only allow set existing scheduler for net.mptcp.scheduler Gregory Detal
2024-04-30 14:00 ` Matthieu Baerts
2024-04-30 12:06 ` [PATCH mptcp-next 2/2] mptcp: add net.mptcp.available_schedulers Gregory Detal
2024-04-30 12:59 ` [PATCH mptcp-next 0/2] mptcp: fix net.mptcp.scheduler behavior MPTCP CI
2024-04-30 14:00 ` Matthieu Baerts
2024-04-30 14:00 ` Matthieu Baerts
2024-05-02 14:16 ` Geliang Tang
2024-05-03 1:04 ` Mat Martineau
2024-05-03 16:45 ` 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=fef27199-7ec3-4390-9a71-9e76e59bc692@kernel.org \
--to=matttbe@kernel.org \
--cc=gregory.detal@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).