MPTCP Linux Development
 help / color / mirror / Atom feed
From: Matthieu Baerts <matttbe@kernel.org>
To: Paolo Abeni <pabeni@redhat.com>
Cc: mptcp@lists.linux.dev
Subject: Re: [PATCH mptcp-net 1/4] mptcp: drop the push_pending field
Date: Thu, 8 Feb 2024 19:05:24 +0100	[thread overview]
Message-ID: <b2433f05-dd95-4a7d-932b-1ff7d351bd58@kernel.org> (raw)
In-Reply-To: <8f4974ba6b07e2313e5a2f521d2ae3810daf4001.camel@redhat.com>

Hi Paolo,

On 08/02/2024 16:12, Paolo Abeni wrote:
> On Thu, 2024-02-08 at 12:36 +0100, Matthieu Baerts wrote:
>> Hi Paolo,
>>
>> On 15/01/2024 16:16, Paolo Abeni wrote:
>>> Such field is there to avoid acquiring the data lock in a few spots,
>>> but if adds complexity to the already non trivial locking schema.
>>>
>>> All the relevant call sites (mptcp-level reinjection, set socket optins),
>>> are slow-path, drop such field in favor of 'cb_flags', adding the relevant
>>> locking.
>>
>> In your cover-letter, you mentioned:
>>
>>> Patch 1 has no fixes, but still is logically tied to the other patches.
>>
>> I think it makes sense to have this patch in -net, especially because it
>> is logically tied to the others. Would it be OK for you if I add:
>>
>>   Fixes: e9d09baca676 ("mptcp: avoid atomic bit manipulation when possible")
> 
> The obove, or add a sentence to the commit message alike:
> 
> """
> This will also simplify the next patch
> """

Good idea! I added both:

> This patch could be seen as an improvement, instead of a fix. But it
> simplifies the next patch. The 'Fixes' tag has been added to help having
> this series backported to stable.

I hope that's OK! :)

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

  reply	other threads:[~2024-02-08 18:05 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-15 15:16 [PATCH mptcp-net 0/4] mptcp: locking cleanup Paolo Abeni
2024-01-15 15:16 ` [PATCH mptcp-net 1/4] mptcp: drop the push_pending field Paolo Abeni
2024-02-08 11:36   ` Matthieu Baerts
2024-02-08 15:12     ` Paolo Abeni
2024-02-08 18:05       ` Matthieu Baerts [this message]
2024-02-08 18:07         ` Paolo Abeni
2024-01-15 15:16 ` [PATCH mptcp-net 2/4] mptcp: fix rcv space initialization Paolo Abeni
2024-01-15 15:16 ` [PATCH mptcp-net 3/4] mptcp: fix more tx path fields initialization Paolo Abeni
2024-01-15 15:16 ` [PATCH mptcp-net 4/4] mptcp: corner case locking for rx " Paolo Abeni
2024-01-15 16:13   ` mptcp: corner case locking for rx path fields initialization: Tests Results MPTCP CI
2024-01-15 17:07   ` MPTCP CI
2024-01-17  2:57   ` MPTCP CI
2024-01-17  3:54   ` MPTCP CI
2024-01-17  7:01   ` MPTCP CI
2024-01-17  2:32 ` [PATCH mptcp-net 0/4] mptcp: locking cleanup Mat Martineau
2024-01-17 10:30   ` Paolo Abeni
2024-01-17 11:58 ` 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=b2433f05-dd95-4a7d-932b-1ff7d351bd58@kernel.org \
    --to=matttbe@kernel.org \
    --cc=mptcp@lists.linux.dev \
    --cc=pabeni@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox