From: Geliang Tang <geliang@kernel.org>
To: Matthieu Baerts <matttbe@kernel.org>, mptcp@lists.linux.dev
Subject: Re: [PATCH iproute2-next] ss: mptcp: print out last time counters
Date: Fri, 12 Apr 2024 11:37:02 +0800 [thread overview]
Message-ID: <27fa348e03f7ba70297f3c154c86a11a622f44f6.camel@kernel.org> (raw)
In-Reply-To: <017fcb6d-6dcc-436b-9c15-f779f84756ad@kernel.org>
Hi Matt,
On Thu, 2024-04-11 at 19:33 +0200, Matthieu Baerts wrote:
> Hi Geliang,
>
> On 29/03/2024 16:01, Matthieu Baerts wrote:
> > Hi Geliang,
> >
> > On 29/03/2024 10:42, Geliang Tang wrote:
> > > There new last time counters have been added in struct mptcp_info
> > > named
> >
> > (I guess we can remove the "There" here above)
It should be "Three".
> >
> > > last_data_sent, last_data_recv and last_ack_recv into kernel in
> > > the commit
> > > "mptcp: add last time fields in mptcp_info".
> > >
> > > This patch prints out these counters into mptcp_stats output.
> >
> > Thank you for this patch!
> >
> > It looks good to me.
> >
> > Acked-by: Matthieu Baerts (NGI0) <matttbe@kernel.org>
> >
> > Of course, we will need to wait for the kernel patch to be in our
> > tree,
> > then in net-next, before sending this one to IPRoute2 maintainers.
>
> The kernel patch has been applied in net-next. Do you want to send
> this
> patch to IPRoute2 maintainers, or do you prefer if I do that?
Please send it for me, thanks.
-Geliang
>
> Cheers,
> Matt
next prev parent reply other threads:[~2024-04-12 3:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-29 9:42 [PATCH iproute2-next] ss: mptcp: print out last time counters Geliang Tang
2024-03-29 15:01 ` Matthieu Baerts
2024-04-11 17:33 ` Matthieu Baerts
2024-04-12 3:37 ` Geliang Tang [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-04-12 8:19 Matthieu Baerts (NGI0)
2024-04-13 16:45 ` David Ahern
2024-04-16 7:36 ` 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=27fa348e03f7ba70297f3c154c86a11a622f44f6.camel@kernel.org \
--to=geliang@kernel.org \
--cc=matttbe@kernel.org \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).