From: Steven Rostedt <rostedt@goodmis.org>
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>
Cc: Yafang Shao <laoar.shao@gmail.com>,
davem@davemloft.net, mingo@redhat.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, songliubraving@fb.com
Subject: Re: [PATCH] net/tcp: introduce TRACE_EVENT for TCP/IPv4 state transition
Date: Thu, 9 Nov 2017 13:18:08 -0500 [thread overview]
Message-ID: <20171109131808.373c296f@gandalf.local.home> (raw)
In-Reply-To: <20171109064326.skfvvohg7qhgl3lp@ast-mbp>
On Thu, 9 Nov 2017 15:43:29 +0900
Alexei Starovoitov <alexei.starovoitov@gmail.com> wrote:
> > +TRACE_EVENT(tcp_set_state,
> > + TP_PROTO(struct sock *sk, int oldstate, int newstate),
> > + TP_ARGS(sk, oldstate, newstate),
> > +
> > + TP_STRUCT__entry(
> > + __field(__be32, dst)
> > + __field(__be32, src)
> > + __field(__u16, dport)
> > + __field(__u16, sport)
> > + __field(int, oldstate)
> > + __field(int, newstate)
> > + ),
> > +
> > + TP_fast_assign(
> > + if (oldstate == TCP_TIME_WAIT) {
> > + __entry->dst = inet_twsk(sk)->tw_daddr;
> > + __entry->src = inet_twsk(sk)->tw_rcv_saddr;
> > + __entry->dport = ntohs(inet_twsk(sk)->tw_dport);
> > + __entry->sport = ntohs(inet_twsk(sk)->tw_sport);
> > + } else if (oldstate == TCP_NEW_SYN_RECV) {
> > + __entry->dst = inet_rsk(inet_reqsk(sk))->ir_rmt_addr;
> > + __entry->src = inet_rsk(inet_reqsk(sk))->ir_loc_addr;
> > + __entry->dport =
> > + ntohs(inet_rsk(inet_reqsk(sk))->ir_rmt_port);
> > + __entry->sport = inet_rsk(inet_reqsk(sk))->ir_num;
> > + } else {
> > + __entry->dst = inet_sk(sk)->inet_daddr;
> > + __entry->src = inet_sk(sk)->inet_rcv_saddr;
> > + __entry->dport = ntohs(inet_sk(sk)->inet_dport);
> > + __entry->sport = ntohs(inet_sk(sk)->inet_sport);
> > + }
> > +
> > + __entry->oldstate = oldstate;
> > + __entry->newstate = newstate;
> > + ),
> > +
> > + TP_printk("%08X:%04X %08X:%04X, %02x %02x",
> > + __entry->src, __entry->sport, __entry->dst, __entry->dport,
> > + __entry->oldstate, __entry->newstate)
>
> direct %x of state is not allowed.
> This has to use show_tcp_state_name() like it's done in trace_tcp_set_state
Hmm, I need to look at trace_tcp_set_state. I'm guessing it is in
net-next too?
>
> Also I'm missing the reason to introduce another tracepoint
> that looks just like trace_tcp_set_state.
I want to make sure that perf and trace-cmd can parse the TP_printk(),
if it is having helper functions like that in the TP_printk() part,
then the libtraceevent needs to be aware of that.
-- Steve
next prev parent reply other threads:[~2017-11-09 18:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-09 6:01 Yafang Shao
2017-11-09 6:43 ` Alexei Starovoitov
2017-11-09 6:50 ` Yafang Shao
2017-11-09 18:18 ` Steven Rostedt [this message]
2017-11-09 18:34 ` Song Liu
2017-11-09 23:40 ` Song Liu
2017-11-10 0:42 ` Steven Rostedt
2017-11-10 0:57 ` [PATCH] tcp: Export to userspace the TCP state names for the trace events Steven Rostedt
2017-11-10 1:42 ` Song Liu
2017-11-10 4:56 ` Yafang Shao
2017-11-10 15:07 ` Steven Rostedt
2017-11-10 17:37 ` Song Liu
2017-11-11 2:06 ` Yafang Shao
2017-11-11 3:32 ` Steven Rostedt
2017-11-11 13:26 ` Yafang Shao
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=20171109131808.373c296f@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=alexei.starovoitov@gmail.com \
--cc=davem@davemloft.net \
--cc=laoar.shao@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=netdev@vger.kernel.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
all inboxes | Powered by JetHome®