From: Matthieu Baerts <matttbe@kernel.org>
To: Geliang Tang <geliang@kernel.org>, mptcp@lists.linux.dev
Cc: Geliang Tang <tanggeliang@kylinos.cn>
Subject: Re: [PATCH mptcp-next v5 0/5] Squash to "Add mptcp_subflow bpf_iter support"
Date: Mon, 3 Mar 2025 12:13:33 +0100 [thread overview]
Message-ID: <c385f08c-15c0-4be1-8d98-0677113e5ccd@kernel.org> (raw)
In-Reply-To: <cover.1740997925.git.tanggeliang@kylinos.cn>
Hi Geliang, Mat,
On 03/03/2025 11:33, Geliang Tang wrote:
> From: Geliang Tang <tanggeliang@kylinos.cn>
>
> v5:
> - check bpf_iter_task in mptcp_subflow_new() as Mat suggested.
Thank you for the modification, but would it not be easier not to do
that in this series, not to increase the complexity?
This can be done in the "use bpf_iter in bpf schedulers" instead, no?
For me, the v4 (with my squash-to patch) is enough to be used with CG
[gs]etsocktopt.
Also, I think the idea is set this marker before calling the future
struct_ops, in places where we know the msk is owned, but not in
bpf_mptcp_sock_from_sock() which doesn't check if the msk is owned, no?
Cheers,
Matt
--
Sponsored by the NGI0 Core fund.
next prev parent reply other threads:[~2025-03-03 11:13 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-03 10:33 [PATCH mptcp-next v5 0/5] Squash to "Add mptcp_subflow bpf_iter support" Geliang Tang
2025-03-03 10:33 ` [PATCH mptcp-next v5 1/5] mptcp: add bpf_iter_task for mptcp_sock Geliang Tang
2025-03-03 10:33 ` [PATCH mptcp-next v5 2/5] Squash to "bpf: Extend bpf_skc_to_mptcp_sock to MPTCP sock" Geliang Tang
2025-03-04 1:37 ` Mat Martineau
2025-03-07 3:51 ` Geliang Tang
2025-03-07 3:54 ` Geliang Tang
2025-03-07 8:53 ` Matthieu Baerts
2025-03-03 10:33 ` [PATCH mptcp-next v5 3/5] Squash to "bpf: Add mptcp_subflow bpf_iter" Geliang Tang
2025-03-04 1:39 ` Mat Martineau
2025-03-07 3:54 ` Geliang Tang
2025-03-03 10:33 ` [PATCH mptcp-next v5 4/5] Revert "bpf: Acquire and release mptcp socket" Geliang Tang
2025-03-03 10:33 ` [PATCH mptcp-next v5 5/5] Squash to "selftests/bpf: Add mptcp_subflow bpf_iter subtest" Geliang Tang
2025-03-03 11:13 ` Matthieu Baerts [this message]
2025-03-03 11:42 ` [PATCH mptcp-next v5 0/5] Squash to "Add mptcp_subflow bpf_iter support" MPTCP CI
-- strict thread matches above, loose matches on Subject: below --
2024-12-11 3:11 Geliang Tang
2024-12-11 4:17 ` MPTCP CI
2024-12-16 12:06 ` Matthieu Baerts
2024-12-16 12:27 ` Matthieu Baerts
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=c385f08c-15c0-4be1-8d98-0677113e5ccd@kernel.org \
--to=matttbe@kernel.org \
--cc=geliang@kernel.org \
--cc=mptcp@lists.linux.dev \
--cc=tanggeliang@kylinos.cn \
/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.