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] Squash to "selftests/bpf: Add mptcp subflow subtest" - set limits
Date: Tue, 30 Jul 2024 11:04:29 +0200 [thread overview]
Message-ID: <fbd22fcf-6856-4b62-89dd-06b04780dc42@kernel.org> (raw)
In-Reply-To: <9dafce3091d30a8446897813d2a9d302625c09d0.1722327628.git.tanggeliang@kylinos.cn>
Hi Geliang,
On 30/07/2024 10:24, Geliang Tang wrote:
> From: Geliang Tang <tanggeliang@kylinos.cn>
>
> Need to set limits before adding endpoints.
Why do we need to do that? Do we not have 2 subflows in these tests?
The default limits are set at 2 additional subflows, is it not enough?
Cheers,
Matt
--
Sponsored by the NGI0 Core fund.
next prev parent reply other threads:[~2024-07-30 9:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-30 8:24 [PATCH mptcp-next] Squash to "selftests/bpf: Add mptcp subflow subtest" - set limits Geliang Tang
2024-07-30 9:04 ` Matthieu Baerts [this message]
2024-07-30 9:14 ` Geliang Tang
2024-07-30 9:15 ` 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=fbd22fcf-6856-4b62-89dd-06b04780dc42@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.