All of lore.kernel.org
 help / color / mirror / Atom feed
From: Geliang Tang <geliang.tang@suse.com>
To: mptcp@lists.linux.dev
Cc: Geliang Tang <geliang.tang@suse.com>
Subject: [PATCH mptcp-next v12 09/10] selftests: bpf: add bpf_first scheduler
Date: Wed, 20 Apr 2022 12:57:08 +0800	[thread overview]
Message-ID: <017efa90a2ddb36d4c9a5b88fb07e6c7bf8b6b7b.1650430389.git.geliang.tang@suse.com> (raw)
In-Reply-To: <cover.1650430388.git.geliang.tang@suse.com>

This patch implements the simplest MPTCP scheduler, named bpf_first,
which always picks the first subflow to send data. It's a sample of
MPTCP BPF scheduler implementations.

Signed-off-by: Geliang Tang <geliang.tang@suse.com>
---
 .../selftests/bpf/progs/mptcp_bpf_first.c     | 34 +++++++++++++++++++
 1 file changed, 34 insertions(+)
 create mode 100644 tools/testing/selftests/bpf/progs/mptcp_bpf_first.c

diff --git a/tools/testing/selftests/bpf/progs/mptcp_bpf_first.c b/tools/testing/selftests/bpf/progs/mptcp_bpf_first.c
new file mode 100644
index 000000000000..425b89c654b2
--- /dev/null
+++ b/tools/testing/selftests/bpf/progs/mptcp_bpf_first.c
@@ -0,0 +1,34 @@
+// SPDX-License-Identifier: GPL-2.0
+/* Copyright (c) 2022, SUSE. */
+
+#include <linux/bpf.h>
+#include "bpf_mptcp_helpers.h"
+
+char _license[] SEC("license") = "GPL";
+
+SEC("struct_ops/mptcp_sched_first_init")
+void BPF_PROG(mptcp_sched_first_init, struct mptcp_sock *msk)
+{
+}
+
+SEC("struct_ops/mptcp_sched_first_release")
+void BPF_PROG(mptcp_sched_first_release, struct mptcp_sock *msk)
+{
+}
+
+struct sock *BPF_STRUCT_OPS(bpf_first_get_subflow, struct mptcp_sock *msk, bool retrans)
+{
+	struct sock *ssk = msk->first;
+
+	msk->last_snd = ssk;
+	msk->call_me_again = 0;
+	return ssk;
+}
+
+SEC(".struct_ops")
+struct mptcp_sched_ops first = {
+	.init		= (void *)mptcp_sched_first_init,
+	.release	= (void *)mptcp_sched_first_release,
+	.get_subflow	= (void *)bpf_first_get_subflow,
+	.name		= "bpf_first",
+};
-- 
2.34.1


  parent reply	other threads:[~2022-04-20  4:58 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-20  4:56 [PATCH mptcp-next v12 00/10] BPF packet scheduler Geliang Tang
2022-04-20  4:57 ` [PATCH mptcp-next v12 01/10] mptcp: add struct mptcp_sched_ops Geliang Tang
2022-04-20 16:22   ` Matthieu Baerts
2022-04-20  4:57 ` [PATCH mptcp-next v12 02/10] mptcp: register default scheduler Geliang Tang
2022-04-20  4:57 ` [PATCH mptcp-next v12 03/10] mptcp: add a new sysctl scheduler Geliang Tang
2022-04-20  4:57 ` [PATCH mptcp-next v12 04/10] mptcp: add sched in mptcp_sock Geliang Tang
2022-04-20  4:57 ` [PATCH mptcp-next v12 05/10] mptcp: add get_subflow wrapper Geliang Tang
2022-04-20  4:57 ` [PATCH mptcp-next v12 06/10] mptcp: add bpf_mptcp_sched_ops Geliang Tang
2022-04-20  4:57 ` [PATCH mptcp-next v12 07/10] mptcp: add last_snd write access Geliang Tang
2022-04-20 16:23   ` Matthieu Baerts
2022-04-20 16:44   ` Matthieu Baerts
2022-04-21  6:42   ` kernel test robot
2022-04-20  4:57 ` [PATCH mptcp-next v12 08/10] mptcp: add call_me_again flag Geliang Tang
2022-04-20 16:40   ` Matthieu Baerts
2022-04-20  4:57 ` Geliang Tang [this message]
2022-04-20  4:57 ` [PATCH mptcp-next v12 10/10] selftests: bpf: add bpf_first test Geliang Tang
2022-04-20  5:14   ` selftests: bpf: add bpf_first test: Build Failure MPTCP CI
2022-04-20  6:49   ` selftests: bpf: add bpf_first test: Tests Results MPTCP CI

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=017efa90a2ddb36d4c9a5b88fb07e6c7bf8b6b7b.1650430389.git.geliang.tang@suse.com \
    --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 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.