From: Eric Dumazet <eric.dumazet@gmail.com>
To: Yafang Shao <laoar.shao@gmail.com>, davem@davemloft.net
Cc: kuznet@ms2.inr.ac.ru, yoshfuji@linux-ipv6.org,
songliubraving@fb.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next] net: introduce a new tracepoint for tcp_rcv_space_adjust
Date: Mon, 16 Apr 2018 08:43:31 -0700 [thread overview]
Message-ID: <d2ab1647-c832-c982-5952-ab7a415f7c76@gmail.com> (raw)
In-Reply-To: <1523892818-12820-1-git-send-email-laoar.shao@gmail.com>
On 04/16/2018 08:33 AM, Yafang Shao wrote:
> tcp_rcv_space_adjust is called every time data is copied to user space,
> introducing a tcp tracepoint for which could show us when the packet is
> copied to user.
> This could help us figure out whether there's latency in user process.
>
> When a tcp packet arrives, tcp_rcv_established() will be called and with
> the existed tracepoint tcp_probe we could get the time when this packet
> arrives.
> Then this packet will be copied to user, and tcp_rcv_space_adjust will
> be called and with this new introduced tracepoint we could get the time
> when this packet is copied to user.
>
> arrives time : user process time => latency caused by user
> tcp_probe tcp_rcv_space_adjust
>
> Hence in the prink message, sk is printed as a key to connect these two
> tracepoints.
>
socket pointer is not a key.
TCP sockets can be reused pretty fast after free.
I suggest you go for cookie instead, this is an unique 64bit identifier.
( sock_gen_cookie() for details )
next prev parent reply other threads:[~2018-04-16 15:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-16 15:33 [PATCH net-next] net: introduce a new tracepoint for tcp_rcv_space_adjust Yafang Shao
2018-04-16 15:43 ` Eric Dumazet [this message]
2018-04-16 16:03 ` Yafang Shao
2018-04-17 23:44 ` Alexei Starovoitov
2018-04-18 4:42 ` Yafang Shao
-- strict thread matches above, loose matches on Subject: below --
2018-04-14 9:48 Yafang Shao
2018-04-14 19:47 ` David Miller
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=d2ab1647-c832-c982-5952-ab7a415f7c76@gmail.com \
--to=eric.dumazet@gmail.com \
--cc=davem@davemloft.net \
--cc=kuznet@ms2.inr.ac.ru \
--cc=laoar.shao@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=songliubraving@fb.com \
--cc=yoshfuji@linux-ipv6.org \
/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