From: Yafang Shao <laoar.shao@gmail.com>
To: songliubraving@fb.com, davem@davemloft.net,
marcelo.leitner@gmail.com, rostedt@goodmis.org
Cc: bgregg@netflix.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, Yafang Shao <laoar.shao@gmail.com>
Subject: [PATCH v3 net-next 0/5] replace tcp_set_state tracepoint with inet_sock_set_state
Date: Wed, 20 Dec 2017 11:12:49 +0800 [thread overview]
Message-ID: <1513739574-3345-1-git-send-email-laoar.shao@gmail.com> (raw)
According to the discussion in the mail thread
https://patchwork.kernel.org/patch/10099243/,
tcp_set_state tracepoint is renamed to inet_sock_set_state tracepoint and is
moved to include/trace/events/sock.h.
With this new tracepoint, we can trace AF_INET/AF_INET6 sock state transitions.
As there's only one single tracepoint for inet, so I didn't create a new trace
file named trace/events/inet_sock.h, and just place it in
include/trace/events/sock.h
Currently TCP/DCCP/SCTP state transitions are traced with this tracepoint.
- Why not more protocol ?
If we really think that anonter protocol should be traced, I will modify the
code to trace it.
I just want to make the code easy and not output useless information.
Steven Rostedt (VMware) (1):
tcp: Export to userspace the TCP state names for the trace events
Yafang Shao (4):
net: tracepoint: replace tcp_set_state tracepoint with
inet_sock_set_state tracepoint
net: sock: replace sk_state_load with inet_sk_state_load and remove
sk_state_store
net: tracepoint: using sock_set_state tracepoint to trace DCCP state
transition
net: tracepoint: using sock_set_state tracepoint to trace SCTP state
transition
include/net/inet_sock.h | 25 ++++++++++
include/net/sock.h | 25 ----------
include/trace/events/sock.h | 107 ++++++++++++++++++++++++++++++++++++++++
include/trace/events/tcp.h | 16 ------
net/dccp/proto.c | 2 +-
net/ipv4/af_inet.c | 14 ++++++
net/ipv4/inet_connection_sock.c | 8 +--
net/ipv4/inet_hashtables.c | 2 +-
net/ipv4/tcp.c | 10 ++--
net/ipv4/tcp_diag.c | 2 +-
net/ipv4/tcp_ipv4.c | 2 +-
net/ipv6/tcp_ipv6.c | 2 +-
net/sctp/endpointola.c | 2 +-
net/sctp/sm_sideeffect.c | 4 +-
net/sctp/socket.c | 12 ++---
15 files changed, 167 insertions(+), 66 deletions(-)
--
1.8.3.1
next reply other threads:[~2017-12-20 3:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-20 3:12 Yafang Shao [this message]
2017-12-20 3:12 ` [PATCH v3 net-next 1/5] tcp: Export to userspace the TCP state names for the trace events Yafang Shao
2017-12-20 3:12 ` [PATCH v3 net-next 2/5] net: tracepoint: replace tcp_set_state tracepoint with inet_sock_set_state tracepoint Yafang Shao
2017-12-30 22:33 ` Brendan Gregg
2017-12-31 3:06 ` Yafang Shao
2018-01-02 19:46 ` Brendan Gregg
2018-01-02 19:52 ` David Miller
2018-01-03 1:48 ` Yafang Shao
2017-12-20 3:12 ` [PATCH v3 net-next 3/5] net: sock: replace sk_state_load with inet_sk_state_load and remove sk_state_store Yafang Shao
2017-12-20 3:12 ` [PATCH v3 net-next 4/5] net: tracepoint: using sock_set_state tracepoint to trace DCCP state transition Yafang Shao
2017-12-20 3:12 ` [PATCH v3 net-next 5/5] net: tracepoint: using sock_set_state tracepoint to trace SCTP " Yafang Shao
2017-12-20 19:00 ` [PATCH v3 net-next 0/5] replace tcp_set_state tracepoint with inet_sock_set_state 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=1513739574-3345-1-git-send-email-laoar.shao@gmail.com \
--to=laoar.shao@gmail.com \
--cc=bgregg@netflix.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.leitner@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=songliubraving@fb.com \
/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