From: Geliang Tang <geliang.tang@suse.com>
To: mptcp@lists.linux.dev
Subject: Re: [PATCH mptcp-next v14 6/7] selftests/bpf: Add bpf_red scheduler
Date: Thu, 20 Oct 2022 11:00:23 +0800 [thread overview]
Message-ID: <20221020030022.GA31465@localhost> (raw)
In-Reply-To: <fa8fa105a91e17b619cafba6b570e2b5b1c42e84.1666185947.git.geliang.tang@suse.com>
On Wed, Oct 19, 2022 at 09:36:04PM +0800, Geliang Tang wrote:
> This patch implements the redundant BPF MPTCP scheduler, named bpf_red,
> which sends all packets redundantly on all available subflows.
>
> Signed-off-by: Geliang Tang <geliang.tang@suse.com>
> ---
> .../selftests/bpf/progs/mptcp_bpf_red.c | 37 +++++++++++++++++++
> 1 file changed, 37 insertions(+)
> create mode 100644 tools/testing/selftests/bpf/progs/mptcp_bpf_red.c
>
> diff --git a/tools/testing/selftests/bpf/progs/mptcp_bpf_red.c b/tools/testing/selftests/bpf/progs/mptcp_bpf_red.c
> new file mode 100644
> index 000000000000..f8a9b4d1630d
> --- /dev/null
> +++ b/tools/testing/selftests/bpf/progs/mptcp_bpf_red.c
> @@ -0,0 +1,37 @@
> +// SPDX-License-Identifier: GPL-2.0
> +/* Copyright (c) 2022, SUSE. */
> +
> +#include <linux/bpf.h>
> +#include "bpf_tcp_helpers.h"
> +
> +char _license[] SEC("license") = "GPL";
> +
> +SEC("struct_ops/mptcp_sched_red_init")
> +void BPF_PROG(mptcp_sched_red_init, const struct mptcp_sock *msk)
> +{
> +}
> +
> +SEC("struct_ops/mptcp_sched_red_release")
> +void BPF_PROG(mptcp_sched_red_release, const struct mptcp_sock *msk)
> +{
> +}
> +
> +void BPF_STRUCT_OPS(bpf_red_get_subflow, const struct mptcp_sock *msk,
> + struct mptcp_sched_data *data)
> +{
> + for (int i = 0; i < MPTCP_SUBFLOWS_MAX; i++) {
> + if (!data->contexts[i])
> + break;
> +
> + mptcp_subflow_set_scheduled(data->contexts[i], true);
> + }
> +}
> +
> +SEC(".struct_ops")
> +struct mptcp_sched_ops red = {
> + .init = (void *)mptcp_sched_red_init,
> + .release = (void *)mptcp_sched_red_release,
> + .data_init = (void *)bpf_red_data_init,
This line should be dropped. Will update in v15.
-Geliang
> + .get_subflow = (void *)bpf_red_get_subflow,
> + .name = "bpf_red",
> +};
> --
> 2.35.3
>
next prev parent reply other threads:[~2022-10-20 3:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-19 13:35 [PATCH mptcp-next v14 0/7] BPF redundant scheduler Geliang Tang
2022-10-19 13:35 ` [PATCH mptcp-next v14 1/7] mptcp: refactor push_pending logic Geliang Tang
2022-10-19 23:30 ` Mat Martineau
2022-10-19 13:36 ` [PATCH mptcp-next v14 2/7] mptcp: use get_send wrapper Geliang Tang
2022-10-19 23:33 ` Mat Martineau
2022-10-19 13:36 ` [PATCH mptcp-next v14 3/7] mptcp: use get_retrans wrapper Geliang Tang
2022-10-19 13:36 ` [PATCH mptcp-next v14 4/7] mptcp: delay updating first_pending Geliang Tang
2022-10-19 13:36 ` [PATCH mptcp-next v14 5/7] mptcp: delay updating already_sent Geliang Tang
2022-10-19 13:36 ` [PATCH mptcp-next v14 6/7] selftests/bpf: Add bpf_red scheduler Geliang Tang
2022-10-20 3:00 ` Geliang Tang [this message]
2022-10-19 13:36 ` [PATCH mptcp-next v14 7/7] selftests/bpf: Add bpf_red test Geliang Tang
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=20221020030022.GA31465@localhost \
--to=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