From: Matthieu Baerts <matttbe@kernel.org>
To: Vastargazing <vebohr@gmail.com>
Cc: martineau@kernel.org, mptcp@lists.linux.dev,
netdev@vger.kernel.org, linux-kselftest@vger.kernel.org,
shuah@kernel.org, stable@vger.kernel.org, fw@strlen.de
Subject: Re: [PATCH] selftests: mptcp: add test for IPv6 subflow SLAB placement
Date: Mon, 4 May 2026 19:44:19 +0200 [thread overview]
Message-ID: <04434fce-df13-4251-b873-60f6fa18474d@kernel.org> (raw)
In-Reply-To: <20260501-reply-mptcp-v6-initcall@vebohr>
Hi Vastargazing,
On 01/05/2026 19:01, Vastargazing wrote:
(...)
> One question if you don't mind: if something similar came up again and
> a test *was* warranted, which existing script would be the natural
> home? mptcp_join.sh seemed closest since it exercises the accept path,
> but i'm not sure if checking /proc/slabinfo fits there or if there's a
> better mechanism for that kind of thing.
It depends on what needs to be covered:
- diag.sh: check various counters
- mptcp_connect.sh: single path
- mptcp_join.sh: multiple paths
- mptcp_sockopt.sh: socket options
- pm_netlink.sh: in-kernel path-manager
- simult_flows.sh: small multiple paths perf tests
- userspace_pm.sh : userspace path-manager
- + kunit: token and crypto
- + packetdrill: various tests
So not mptcp_join.sh. Maybe diag.sh, or in packetdrill.
Cheers,
Matt
--
Sponsored by the NGI0 Core fund.
next prev parent reply other threads:[~2026-05-04 17:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-01 15:14 [PATCH] selftests: mptcp: add test for IPv6 subflow SLAB placement Vastargazing
2026-05-01 15:45 ` Matthieu Baerts
2026-05-01 17:01 ` Vastargazing
2026-05-04 17:44 ` Matthieu Baerts [this message]
2026-05-01 16:29 ` MPTCP CI
-- strict thread matches above, loose matches on Subject: below --
2026-05-01 15:14 Vastargazing
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=04434fce-df13-4251-b873-60f6fa18474d@kernel.org \
--to=matttbe@kernel.org \
--cc=fw@strlen.de \
--cc=linux-kselftest@vger.kernel.org \
--cc=martineau@kernel.org \
--cc=mptcp@lists.linux.dev \
--cc=netdev@vger.kernel.org \
--cc=shuah@kernel.org \
--cc=stable@vger.kernel.org \
--cc=vebohr@gmail.com \
/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.