From: Steven Rostedt <rostedt@goodmis.org>
To: menglong8.dong@gmail.com
Cc: kuba@kernel.org, davem@davemloft.net, mingo@redhat.com,
yoshfuji@linux-ipv6.org, dsahern@kernel.org,
imagedong@tencent.com, ycheng@google.com, kuniyu@amazon.co.jp,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH v2 net-next 0/2] net: snmp: tracepoint support for snmp
Date: Thu, 18 Nov 2021 09:46:28 -0500 [thread overview]
Message-ID: <20211118094628.4e445ef6@gandalf.local.home> (raw)
In-Reply-To: <20211118124812.106538-1-imagedong@tencent.com>
On Thu, 18 Nov 2021 20:48:10 +0800
menglong8.dong@gmail.com wrote:
> nc-171 [000] ..s1. 35.952997: snmp: skbaddr=(____ptrval____), type=9, field=2, val=1
> nc-171 [000] .N... 35.957006: snmp: skbaddr=(____ptrval____), type=9, field=4, val=1
> nc-171 [000] ..s1. 35.957822: snmp: skbaddr=(____ptrval____), type=9, field=2, val=1
> nc-171 [000] ..... 35.957893: snmp: skbaddr=(____ptrval____), type=9, field=4, val=1
>
> 'type=9' means that the event is triggered by udp statistics and 'field=2'
> means that this is triggered by 'NoPorts'. 'val=1' means that increases
> of statistics (decrease can happen on tcp).
Instead of printing numbers, why not print the meanings?
I'll reply to the other patches to explain that.
-- Steve
next prev parent reply other threads:[~2021-11-18 14:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-18 12:48 [PATCH v2 net-next 0/2] net: snmp: tracepoint support for snmp menglong8.dong
2021-11-18 12:48 ` [PATCH v2 net-next 1/2] net: snmp: add " menglong8.dong
2021-11-18 15:57 ` Steven Rostedt
2021-11-18 12:48 ` [PATCH v2 net-next 2/2] net: snmp: add snmp tracepoint support for udp menglong8.dong
2021-11-18 14:46 ` Steven Rostedt [this message]
2021-11-18 15:36 ` [PATCH v2 net-next 0/2] net: snmp: tracepoint support for snmp David Ahern
2021-11-19 3:45 ` Menglong Dong
2021-11-19 3:54 ` David Ahern
2021-11-21 10:47 ` Menglong Dong
2021-11-21 14:02 ` Steven Rostedt
2021-11-22 16:42 ` David Ahern
2021-11-24 2:56 ` Menglong Dong
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=20211118094628.4e445ef6@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=imagedong@tencent.com \
--cc=kuba@kernel.org \
--cc=kuniyu@amazon.co.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=menglong8.dong@gmail.com \
--cc=mingo@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=ycheng@google.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;
as well as URLs for NNTP newsgroup(s).