MPTCP Linux Development
 help / color / mirror / Atom feed
From: Mat Martineau <mathew.j.martineau at linux.intel.com>
To: mptcp at lists.01.org
Subject: [MPTCP] Re: [PATCH] squashto: mptcp: schedule worker when subflow is closed
Date: Wed, 10 Feb 2021 10:03:38 -0800	[thread overview]
Message-ID: <3d8abe11-5695-d263-14aa-bcf1dec517ec@linux.intel.com> (raw)
In-Reply-To: 02ea6762-b88f-60ee-356f-40358d31818d@tessares.net

[-- Attachment #1: Type: text/plain, Size: 1127 bytes --]

On Wed, 10 Feb 2021, Matthieu Baerts wrote:

> Hi Paolo,
>
> On 10/02/2021 17:04, Paolo Abeni wrote:
>> On Wed, 2021-02-10 at 13:47 +0100, Florian Westphal wrote:
>>> When remote side closes a subflow we should schedule the worker to
>>> dispose of the subflow in a timely manner.
>>> 
>>> Otherwise, SF_CLOSED event won't be generated until the mptcp
>>> socket itself is closing or local side is closing another subflow.
>>> 
>>> As noted by Paolo and Matthieu, a subflow that moves to TCP_CLOSE state
>>> might still have data in its rx queue.
>
> (...)
>
>> 
>> LGTM!
>> 
>> @Matttbe: could you please double check this one vs issues/154?
>
> Sure! I should have commented here instead of on GH :)
> I ran this for more than 3h now and I was not able to reproduce this issue! I 
> just stopped the loop.
>
> It looks good to me but I prefer to wait for Mat's ACK as he was the reviewer 
> of the original patch. I can always remove his RvB tag and re-add it later if 
> needed.
>
> Thanks for your work!
>

Ack from me as well - please squash and keep the RvB!


--
Mat Martineau
Intel

             reply	other threads:[~2021-02-10 18:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-10 18:03 Mat Martineau [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-02-10 19:06 [MPTCP] Re: [PATCH] squashto: mptcp: schedule worker when subflow is closed Matthieu Baerts
2021-02-10 16:11 Matthieu Baerts
2021-02-10 16:04 Paolo Abeni

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=3d8abe11-5695-d263-14aa-bcf1dec517ec@linux.intel.com \
    --to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox