MPTCP Linux Development
 help / color / mirror / Atom feed
From: Mat Martineau <mathew.j.martineau@linux.intel.com>
To: Menglong Dong <menglong8.dong@gmail.com>
Cc: mptcp@lists.linux.dev, Menglong Dong <imagedong@tencent.com>
Subject: Re: [PATCH mptcp-next v5 2/3] mptcp: add statistics for mptcp socket in use
Date: Tue, 11 Oct 2022 17:51:51 -0700 (PDT)	[thread overview]
Message-ID: <c50e018e-0ab1-5003-5a0f-1abc971d99e5@linux.intel.com> (raw)
In-Reply-To: <CADxym3bWocKAT7A+76vr84GTiZgMdDR4suYYM9=cABwQZir36g@mail.gmail.com>

On Tue, 11 Oct 2022, Menglong Dong wrote:

> On Tue, Oct 11, 2022 at 9:11 AM Mat Martineau
> <mathew.j.martineau@linux.intel.com> wrote:
>>
>> On Fri, 7 Oct 2022, menglong8.dong@gmail.com wrote:
>>
>>> From: Menglong Dong <imagedong@tencent.com>
>>>
>>> Do the statistics of mptcp socket in use with sock_prot_inuse_add().
>>> Therefore, we can get the count of used mptcp socket from
>>> /proc/net/protocols:
>>>
>>> & cat /proc/net/protocols
>>> protocol  size sockets  memory press maxhdr  slab module     cl co di ac io in de sh ss gs se re sp bi br ha uh gp em
>>> MPTCPv6   2048      0       0   no       0   yes  kernel      y  n  y  y  y  y  y  y  y  y  y  y  n  n  n  y  y  y  n
>>> MPTCP     1896      1       0   no       0   yes  kernel      y  n  y  y  y  y  y  y  y  y  y  y  n  n  n  y  y  y  n
>>>
>>> Signed-off-by: Menglong Dong <imagedong@tencent.com>
>>> ---
>>> v5:
>>> - rebase to solve merge conflict
>>>
>>> v4:
>>> - rename MPTCP_DESTROIED to MPTCP_DESTROYED
>>>
>>> v2:
>>> - decrease the statistics for listening mptcp socket inuse with
>>>  mptcp_listen_inuse_dec()
>>> - add MPTCP_DESTROIED flags to store if mptcp_destroy_common() was
>>>  called on the msk. For fallback case, we need to decrease the
>>>  statistics only once, and mptcp_destroy_common() can be called
>>>  more than once.
>>> ---
>>> net/mptcp/protocol.c | 22 +++++++++++++++++++++-
>>> net/mptcp/protocol.h |  1 +
>>> net/mptcp/subflow.c  |  3 +++
>>> 3 files changed, 25 insertions(+), 1 deletion(-)
>>>
>>> diff --git a/net/mptcp/protocol.c b/net/mptcp/protocol.c
>>> index 04d92dc0941f..3d1570a9d3e9 100644
>>> --- a/net/mptcp/protocol.c
>>> +++ b/net/mptcp/protocol.c
>>> @@ -2974,6 +2974,16 @@ static void mptcp_copy_inaddrs(struct sock *msk, const struct sock *ssk)
>>>       inet_sk(msk)->inet_rcv_saddr = inet_sk(ssk)->inet_rcv_saddr;
>>> }
>>>
>>> +static void mptcp_listen_inuse_dec(struct sock *sk)
>>> +{
>>> +     struct mptcp_sock *msk = mptcp_sk(sk);
>>> +     struct socket *ssock;
>>> +
>>> +     ssock = __mptcp_nmpc_socket(msk);
>>> +     if (ssock && inet_sk_state_load(ssock->sk) == TCP_LISTEN)
>>> +             sock_prot_inuse_add(sock_net(sk), sk->sk_prot, -1);
>>> +}
>>> +
>>> static int mptcp_disconnect(struct sock *sk, int flags)
>>> {
>>>       struct mptcp_sock *msk = mptcp_sk(sk);
>>> @@ -2986,6 +2996,7 @@ static int mptcp_disconnect(struct sock *sk, int flags)
>>>       if (mptcp_sk(sk)->token)
>>>               mptcp_event(MPTCP_EVENT_CLOSED, mptcp_sk(sk), NULL, GFP_KERNEL);
>>>
>>> +     mptcp_listen_inuse_dec(sk);
>>>       /* msk->subflow is still intact, the following will not free the first
>>>        * subflow
>>>        */
>>> @@ -3160,6 +3171,11 @@ void mptcp_destroy_common(struct mptcp_sock *msk, unsigned int flags)
>>>       skb_rbtree_purge(&msk->out_of_order_queue);
>>>       mptcp_data_unlock(sk);
>>>
>>> +     if ((__mptcp_check_fallback(msk) &&
>>> +          !test_and_set_bit(MPTCP_DESTROYED, &msk->flags)) ||
>>
>> Hi Menglong -
>>
>> Sorry I didn't look at this more closely earlier, but did you find that
>> mptcp_destroy_common() is only called multiple times with fallback
>> sockets?
>>
>> (This makes me wonder if we have a separate bug to look at, not
>> necessarily related to your patch series)
>
> Hello,
>
> mptcp_destroy_common() can be called multiple times with all
> sockets, if shutdown is called before close(). Isn't it designed that
> mptcp_destroy_common() can be called multiple times?
>

It did look like mptcp_destroy_common() would work fine with multiple 
calls, but I had forgotten about the expected shutdown/close case.

> For no-fallback sockets, it will be unhashed when mptcp_destroy_common()
> is called for the first time. So we can check if it is in use by this.
>

That makes sense, thanks for the details!

- Mat

>>> +         !sk_unhashed(sk))
>>> +             sock_prot_inuse_add(sock_net(sk), sk->sk_prot, -1);
>>> +
>>>       /* move all the rx fwd alloc into the sk_mem_reclaim_final in
>>>        * inet_sock_destruct() will dispose it
>>>        */
>>> @@ -3174,6 +3190,7 @@ static void mptcp_destroy(struct sock *sk)
>>> {
>>>       struct mptcp_sock *msk = mptcp_sk(sk);
>>>
>>> +     mptcp_listen_inuse_dec(sk);
>>>       /* clears msk->subflow, allowing the following to close
>>>        * even the initial subflow
>>>        */
>>> @@ -3529,6 +3546,7 @@ static int mptcp_connect(struct sock *sk, struct sockaddr *uaddr, int addr_len)
>>>
>>>       mptcp_token_destroy(msk);
>>>       inet_sk_state_store(sk, TCP_SYN_SENT);
>>> +     sock_prot_inuse_add(sock_net(sk), sk->sk_prot, 1);
>>>       subflow = mptcp_subflow_ctx(ssock->sk);
>>> #ifdef CONFIG_TCP_MD5SIG
>>>       /* no MPTCP if MD5SIG is enabled on this socket or we may run out of
>>> @@ -3661,8 +3679,10 @@ static int mptcp_listen(struct socket *sock, int backlog)
>>>
>>>       err = ssock->ops->listen(ssock, backlog);
>>>       inet_sk_state_store(sk, inet_sk_state_load(ssock->sk));
>>> -     if (!err)
>>> +     if (!err) {
>>> +             sock_prot_inuse_add(sock_net(sk), sk->sk_prot, 1);
>>>               mptcp_copy_inaddrs(sk, ssock->sk);
>>> +     }
>>>
>>> unlock:
>>>       release_sock(sk);
>>> diff --git a/net/mptcp/protocol.h b/net/mptcp/protocol.h
>>> index 18f866b1afda..374ef75e4bb9 100644
>>> --- a/net/mptcp/protocol.h
>>> +++ b/net/mptcp/protocol.h
>>> @@ -116,6 +116,7 @@
>>> #define MPTCP_WORK_EOF                3
>>> #define MPTCP_FALLBACK_DONE   4
>>> #define MPTCP_WORK_CLOSE_SUBFLOW 5
>>> +#define MPTCP_DESTROYED              6
>>>
>>> /* MPTCP socket release cb flags */
>>> #define MPTCP_PUSH_PENDING    1
>>> diff --git a/net/mptcp/subflow.c b/net/mptcp/subflow.c
>>> index 07dd23d0fe04..da6cfa73a3bd 100644
>>> --- a/net/mptcp/subflow.c
>>> +++ b/net/mptcp/subflow.c
>>> @@ -747,6 +747,9 @@ static struct sock *subflow_syn_recv_sock(const struct sock *sk,
>>>                       mptcp_sk(new_msk)->setsockopt_seq = ctx->setsockopt_seq;
>>>                       mptcp_pm_new_connection(mptcp_sk(new_msk), child, 1);
>>>                       mptcp_token_accept(subflow_req, mptcp_sk(new_msk));
>>> +                     sock_prot_inuse_add(sock_net(new_msk),
>>> +                                         new_msk->sk_prot,
>>> +                                         1);
>>>                       ctx->conn = new_msk;
>>>                       new_msk = NULL;
>>>
>>> --
>>> 2.37.2
>>>
>>>
>>
>> --
>> Mat Martineau
>> Intel
>

--
Mat Martineau
Intel

  reply	other threads:[~2022-10-12  0:51 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-07  9:29 [PATCH mptcp-next v5 0/3] mptcp: add statistics for mptcp socket in use menglong8.dong
2022-10-07  9:29 ` [PATCH mptcp-next v5 1/3] mptcp: introduce 'sk' to replace 'sock->sk' in mptcp_listen() menglong8.dong
2022-10-07  9:29 ` [PATCH mptcp-next v5 2/3] mptcp: add statistics for mptcp socket in use menglong8.dong
2022-10-11  1:11   ` Mat Martineau
2022-10-11  2:23     ` Menglong Dong
2022-10-12  0:51       ` Mat Martineau [this message]
2022-10-07  9:29 ` [PATCH mptcp-next v5 3/3] selftest: mptcp: add test " menglong8.dong
2022-10-07 10:57   ` selftest: mptcp: add test for mptcp socket in use: Tests Results MPTCP CI
2022-10-12  2:24   ` MPTCP CI
2022-10-12 11:31   ` [PATCH mptcp-next v5 3/3] selftest: mptcp: add test for mptcp socket in use Matthieu Baerts
2022-10-12  0:53 ` [PATCH mptcp-next v5 0/3] mptcp: add statistics " Mat Martineau
2022-10-12  9:29   ` Matthieu Baerts
2022-10-12 10:13     ` Menglong Dong
2022-10-28  3:18     ` Menglong Dong
2022-10-31 17:07       ` Matthieu Baerts
2022-11-01 11:54         ` Menglong Dong

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=c50e018e-0ab1-5003-5a0f-1abc971d99e5@linux.intel.com \
    --to=mathew.j.martineau@linux.intel.com \
    --cc=imagedong@tencent.com \
    --cc=menglong8.dong@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox