[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAL+tcoBHT+BegR2jyohdg8ENP4xN5vYF+0YbWUQV_3ioyKT2uQ@mail.gmail.com>
Date: Fri, 31 May 2024 14:36:16 +0800
From: Jason Xing <kerneljasonxing@...il.com>
To: Eric Dumazet <edumazet@...gle.com>
Cc: kuba@...nel.org, pabeni@...hat.com, davem@...emloft.net,
dsahern@...nel.org, matttbe@...nel.org, martineau@...nel.org,
geliang@...nel.org, netdev@...r.kernel.org, mptcp@...ts.linux.dev,
Jason Xing <kernelxing@...cent.com>
Subject: Re: [PATCH net v3 2/2] mptcp: count CLOSE-WAIT sockets for MPTCP_MIB_CURRESTAB
On Fri, May 31, 2024 at 2:26 PM Eric Dumazet <edumazet@...gle.com> wrote:
>
> On Thu, May 30, 2024 at 3:13 PM Jason Xing <kerneljasonxing@...il.com> wrote:
> >
> > From: Jason Xing <kernelxing@...cent.com>
> >
> > Like previous patch does in TCP, we need to adhere to RFC 1213:
> >
> > "tcpCurrEstab OBJECT-TYPE
> > ...
> > The number of TCP connections for which the current state
> > is either ESTABLISHED or CLOSE- WAIT."
> >
> > So let's consider CLOSE-WAIT sockets.
> >
> > The logic of counting
> > When we increment the counter?
> > a) Only if we change the state to ESTABLISHED.
> >
> > When we decrement the counter?
> > a) if the socket leaves ESTABLISHED and will never go into CLOSE-WAIT,
> > say, on the client side, changing from ESTABLISHED to FIN-WAIT-1.
> > b) if the socket leaves CLOSE-WAIT, say, on the server side, changing
> > from CLOSE-WAIT to LAST-ACK.
> >
> > Fixes: 1da177e4c3f4 ("Linux-2.6.12-rc2")
>
> MPTCP was not part of linux at that time.
Oh, right, thank you.
It should be:
Fixes: d9cd27b8cd19 ("mptcp: add CurrEstab MIB counter support")
I'll fix it soon.
Thanks,
Jason
Powered by blists - more mailing lists