public inbox for mptcp@lists.linux.dev
 help / color / mirror / Atom feed
From: Matthieu Baerts <matttbe@kernel.org>
To: Geliang Tang <geliang@kernel.org>,
	Mat Martineau <martineau@kernel.org>,
	Paolo Abeni <pabeni@redhat.com>
Cc: Gang Yan <yangang@kylinos.cn>, mptcp@lists.linux.dev
Subject: Re: [PATCH mptcp-next v2 2/3] mptcp: allow overridden write_space to be invoked
Date: Tue, 3 Feb 2026 10:42:47 +0100	[thread overview]
Message-ID: <3a02e802-56c6-4c99-8f7d-aa618a8f46b7@kernel.org> (raw)
In-Reply-To: <9a2ce3981452685fe178892d0631b289b8d55e01.camel@kernel.org>

Hi Geliang,

On 03/02/2026 07:54, Geliang Tang wrote:
> Hi Matt, Mat, Paolo,
> 
> On Sun, 2026-01-04 at 13:29 +0800, Geliang Tang wrote:
>> From: Geliang Tang <tanggeliang@kylinos.cn>
>>
>> psock may override its own sk_write_space functions. This patch
>> ensures
>> that the overridden sk_write_space can be invoked by MPTCP.
>>
>> Note: This patch was initially included in the NVME MPTCP set.
> 
> This patch was initially developed to resolve the "timeout" errors
> observed in the NVMe MPTCP tests described in [1], because NVMe TCP
> overrides its own sk_write_space. During subsequent development, I
> discovered that not only NVMe TCP overrides its own sk_write_space, but
> KTLS and psock also override it. 
> 
> Therefore, this patch is needed in all three series. To reduce
> dependencies between these three series, I propose to merge this patch
> into the mainline first.

Just to be sure, when you say "mainline", do you mean our MPTCP tree
with the export branch?

Because we are at the end of a cycle here, my priority is to flush
patches that are ready or fix issues. If I'm not mistaken, this patch is
needed for new features that are not in our tree, not in net or net-next
trees, right?

Cheers,
Matt
-- 
Sponsored by the NGI0 Core fund.


  reply	other threads:[~2026-02-03  9:42 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-04  5:29 [PATCH mptcp-next v2 0/3] implement psock_update_sk_prot Geliang Tang
2026-01-04  5:29 ` [PATCH mptcp-next v2 1/3] mptcp: " Geliang Tang
2026-01-04  5:29 ` [PATCH mptcp-next v2 2/3] mptcp: allow overridden write_space to be invoked Geliang Tang
2026-02-03  6:54   ` Geliang Tang
2026-02-03  9:42     ` Matthieu Baerts [this message]
2026-02-03 10:31       ` Geliang Tang
2026-02-03 10:56         ` Matthieu Baerts
2026-02-03 11:13           ` Matthieu Baerts
2026-02-03 11:14             ` Matthieu Baerts
2026-02-04 11:56   ` Matthieu Baerts
2026-02-05  9:46     ` Geliang Tang
2026-01-04  5:29 ` [PATCH mptcp-next v2 3/3] selftests/bpf: Update sockmap tests for MPTCP Geliang Tang
2026-01-04  6:38 ` [PATCH mptcp-next v2 0/3] implement psock_update_sk_prot 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=3a02e802-56c6-4c99-8f7d-aa618a8f46b7@kernel.org \
    --to=matttbe@kernel.org \
    --cc=geliang@kernel.org \
    --cc=martineau@kernel.org \
    --cc=mptcp@lists.linux.dev \
    --cc=pabeni@redhat.com \
    --cc=yangang@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox