All of lore.kernel.org
 help / color / mirror / Atom feed
From: gang.yan@linux.dev
To: mptcp@lists.linux.dev
Subject: Re: [PATCH mptcp-net v5 1/5] mptcp: replace backlog_list with backlog_queue
Date: Tue, 21 Apr 2026 01:26:48 +0000	[thread overview]
Message-ID: <b3676878753b1956701d07b6010a21fb77c4db83@linux.dev> (raw)
In-Reply-To: <2a14005f-a0ef-4a1a-a13c-f7237f0659ec@redhat.com>

April 20, 2026 at 6:33 PM, "Paolo Abeni" <pabeni@redhat.com mailto:pabeni@redhat.com?to=%22Paolo%20Abeni%22%20%3Cpabeni%40redhat.com%3E > wrote:


> 
> On 4/20/26 11:41 AM, gang.yan@linux.dev wrote:
> 
> > 
> > April 20, 2026 at 5:34 PM, "Paolo Abeni" <pabeni@redhat.com mailto:pabeni@redhat.com?to=%22Paolo%20Abeni%22%20%3Cpabeni%40redhat.com%3E > wrote:
> >  Regarding the TCP-style mechanisms like 'tcp_prune_queue' for handling full
> >  rcvbuf conditions — I have actually attempted similar implementations before.
> >  As you pointed out, this approach is indeed highly complex for MPTCP. There
> >  are far too many aspects that require careful modification and consideration,
> >  making it extremely challenging to implement correctly.
> > 
> > > 
> > > I agree duplicating the TCP pruning code inside MPTCP does not look a
> > >  viable solution.
> > > 
> > >  I think we can instead share it (at least the most cumbersome helper),
> > >  with some caveat. I have a few very rough patches doing that. Let me add
> > >  some comments to at least somehow make the code readable and I'll share
> > >  them here.
> > > 
> >  
> >  Thank you so much for your help and for working on this!
> > 
> Thank you indeed for all the effort and the patience to cope with my
> slow feedback.
> 
> Also I hope it's clear that the goal is trying to find the "best
> possible" solution and it's _not_ preventing or steeling your (much
> appreciated) work!
> 
> Cheers,
> 
> Paolo
>
Thank you very much for your understanding and patience throughout
the review process.It’s clear to me that we share the same goal:
to find the best and most robust solution. I really value your
feedback and guidance, and I will test your new patch as soon as
possible and provide feedback promptly.

Thanks again for your time and support.

Best regards,
Gang

  reply	other threads:[~2026-04-21  1:26 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-01  8:54 [PATCH mptcp-net v5 0/5] mptcp: fix stall because of data_ready Gang Yan
2026-04-01  8:54 ` [PATCH mptcp-net v5 1/5] mptcp: replace backlog_list with backlog_queue Gang Yan
2026-04-01 20:12   ` Paolo Abeni
2026-04-15  7:17     ` Paolo Abeni
2026-04-15  8:21       ` gang.yan
2026-04-20  9:34         ` Paolo Abeni
2026-04-20  9:41           ` gang.yan
2026-04-20 10:33             ` Paolo Abeni
2026-04-21  1:26               ` gang.yan [this message]
2026-04-01  8:54 ` [PATCH mptcp-net v5 2/5] mptcp: fix the stall problems using backlog_queue Gang Yan
2026-04-01  8:54 ` [PATCH mptcp-net v5 3/5] mptcp: fix the stall problems with data_ready Gang Yan
2026-04-01  8:54 ` [PATCH mptcp-net v5 4/5] mptcp: fix the dead_lock in mptcp_data_ready Gang Yan
2026-04-01 20:02   ` Paolo Abeni
     [not found]     ` <e1f58d941ad141f9f96a24d1a1d9d6ca74cc2f5e@linux.dev>
2026-04-03  6:45       ` Fwd: " gang.yan
2026-04-13 15:49         ` Paolo Abeni
2026-04-01  8:54 ` [PATCH mptcp-net v5 5/5] selftests: mptcp: test transmission with small rcvbuf Gang Yan
2026-04-03  1:17   ` Geliang Tang
2026-04-03  8:52     ` 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=b3676878753b1956701d07b6010a21fb77c4db83@linux.dev \
    --to=gang.yan@linux.dev \
    --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.