All of lore.kernel.org
 help / color / mirror / Atom feed
From: Geliang Tang <geliang.tang@suse.com>
To: Matthieu Baerts <matthieu.baerts@tessares.net>
Cc: Mat Martineau <mathew.j.martineau@linux.intel.com>,
	mptcp@lists.linux.dev
Subject: Re: [PATCH mptcp-next v2 00/14] update bpf patches on export branch
Date: Sat, 14 May 2022 23:48:45 +0800	[thread overview]
Message-ID: <20220514154845.GA4189@bogon.HOST> (raw)
In-Reply-To: <8f2755bc-4c52-9837-c0db-2b620d7a3b22@tessares.net>

On Sat, May 14, 2022 at 01:25:35PM +0200, Matthieu Baerts wrote:
> Hi Geliang, Mat
> 
> On 11/05/2022 09:56, Geliang Tang wrote:
> > v2:
> >  - drop "bpf: expose is_mptcp flag to bpf_tcp_sock" (Martin & Andrii)
> >  - patch 3, use is_mptcp in tcp_sock, instead of bpf_tcp_sock (Martin & Andrii)
> > 
> > base-commit: bcf89bc9c28e ("DO-NOT-MERGE: git markup: features
> > net-next-next") on export/20220510T054929
> > 
> > v1:
> >  - drop bpf_mptcp_helpers.h (Andrii)
> >  - patch 6, skip the test if 'ip mptcp monitor' is not supported (Mat)
> 
> Thank you for the patches.
> 
> I *think* everything is now sync in our tree but feel free to check
> because I had to "manually" compare patches with what was in our tree.
> 
> But in theory, our tree is now ready for a v5.

Thanks Matt, but three patches still need to be updated:

Patch #4, selftests/bpf: test bpf_skc_to_mptcp_sock

if (!tcp_sk->is_mptcp) {

->

if (!is_mptcp) {

Patch #10, mptcp: add sched in mptcp_sock

 struct mptcp_sock {
 	struct inet_connection_sock	sk;
 
-	__u32		token;
-	struct sock	*first;
-	char		ca_name[TCP_CA_NAME_MAX];
+	__u32			token;
+	struct sock		*first;
+	struct mptcp_sched_ops	*sched;
+	char			ca_name[TCP_CA_NAME_MAX];
 } __attribute__((preserve_access_index));
 
->

 	__u32		token;
 	struct sock	*first;
+	struct mptcp_sched_ops *sched;
 	char		ca_name[TCP_CA_NAME_MAX];
 } __attribute__((preserve_access_index));
 

Patch #13, selftests/bpf: add bpf_first scheduler

bpf_mptcp_helpers.h

->

bpf_tcp_helpers.h

Thanks,
-Geliang

> 
> - 82041505ae27: tg:msg: changelog v4
> - a59272c197c5: selftests/bpf: add MPTCP test base
> - e30677603c0a: Squash to "selftests/bpf: add MPTCP test base"
> - 79399587d58f: tg:msg: changelog v4
> - b0d947191559: selftests/bpf: verify token of struct mptcp_sock
> - d84ab981b155: conflict in
> t/selftests-bpf-verify-first-of-struct-mptcp_sock
> - 0c8b3a796796: conflict in t/selftests-bpf-test-bpf_skc_to_mptcp_sock
> - Results: 7809acd805cf..a4159e050cd2 (export)
> 
> Builds and tests are now in progress:
> 
> https://cirrus-ci.com/github/multipath-tcp/mptcp_net-next/export/20220514T112122
> https://github.com/multipath-tcp/mptcp_net-next/actions/workflows/build-validation.yml?query=branch:export
> 
> Cheers,
> Matt
> -- 
> Tessares | Belgium | Hybrid Access Solutions
> www.tessares.net
> 


  reply	other threads:[~2022-05-14 15:48 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-11  7:56 [PATCH mptcp-next v2 00/14] update bpf patches on export branch Geliang Tang
2022-05-11  7:56 ` [PATCH mptcp-next v2 01/14] bpf: add bpf_skc_to_mptcp_sock_proto Geliang Tang
2022-05-11  7:56 ` [PATCH mptcp-next v2 02/14] selftests/bpf: Enable CONFIG_IKCONFIG_PROC in config Geliang Tang
2022-05-11  7:56 ` [PATCH mptcp-next v2 03/14] selftests/bpf: add MPTCP test base Geliang Tang
2022-05-11  7:56 ` [PATCH mptcp-next v2 04/14] selftests/bpf: test bpf_skc_to_mptcp_sock Geliang Tang
2022-05-11  7:56 ` [PATCH mptcp-next v2 05/14] selftests/bpf: verify token of struct mptcp_sock Geliang Tang
2022-05-11  7:56 ` [PATCH mptcp-next v2 06/14] selftests/bpf: verify ca_name " Geliang Tang
2022-05-11  7:56 ` [PATCH mptcp-next v2 07/14] selftests/bpf: verify first " Geliang Tang
2022-05-11  7:56 ` [PATCH mptcp-next v2 08/14] mptcp: add struct mptcp_sched_ops Geliang Tang
2022-05-11  7:56 ` [PATCH mptcp-next v2 09/14] mptcp: add a new sysctl scheduler Geliang Tang
2022-05-11  7:56 ` [PATCH mptcp-next v2 10/14] mptcp: add sched in mptcp_sock Geliang Tang
2022-05-11  7:56 ` [PATCH mptcp-next v2 11/14] mptcp: add get_subflow wrappers Geliang Tang
2022-05-11  7:56 ` [PATCH mptcp-next v2 12/14] mptcp: add bpf_mptcp_sched_ops Geliang Tang
2022-05-11  7:56 ` [PATCH mptcp-next v2 13/14] selftests/bpf: add bpf_first scheduler Geliang Tang
2022-05-11  7:56 ` [PATCH mptcp-next v2 14/14] selftests/bpf: add bpf_first test Geliang Tang
2022-05-12  0:17 ` [PATCH mptcp-next v2 00/14] update bpf patches on export branch Mat Martineau
2022-05-14 11:25 ` Matthieu Baerts
2022-05-14 15:48   ` Geliang Tang [this message]
2022-05-14 16:31     ` Matthieu Baerts
2022-05-14 16:46       ` Geliang Tang
2022-05-16  2:20         ` Geliang Tang
2022-05-16  5:56       ` 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=20220514154845.GA4189@bogon.HOST \
    --to=geliang.tang@suse.com \
    --cc=mathew.j.martineau@linux.intel.com \
    --cc=matthieu.baerts@tessares.net \
    --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.