From: Paolo Abeni <pabeni@redhat.com>
To: Johannes Berg <johannes@sipsolutions.net>, linux-kernel@vger.kernel.org
Cc: linux-trace-kernel@vger.kernel.org, netdev@vger.kernel.org,
linux-wireless@vger.kernel.org,
Johannes Berg <johannes.berg@intel.com>
Subject: Re: [PATCH v5 3/4] net: dropreason: use new __print_sym() in tracing
Date: Tue, 18 Jun 2024 10:26:11 +0200 [thread overview]
Message-ID: <294c30a62d415c9b641be32df2b527cfff19ef62.camel@redhat.com> (raw)
In-Reply-To: <20240614081956.19832-8-johannes@sipsolutions.net>
On Fri, 2024-06-14 at 10:19 +0200, Johannes Berg wrote:
> From: Johannes Berg <johannes.berg@intel.com>
>
> The __print_symbolic() could only ever print the core
> drop reasons, since that's the way the infrastructure
> works. Now that we have __print_sym() with all the
> advantages mentioned in that commit, convert to that
> and get all the drop reasons from all subsystems. As
> we already have a list of them, that's really easy.
>
> This is a little bit of .text (~100 bytes in my build)
> and saves a lot of .data (~17k).
>
> Signed-off-by: Johannes Berg <johannes.berg@intel.com>
> ---
> include/net/dropreason.h | 5 +++++
> include/trace/events/skb.h | 16 +++-----------
> net/core/skbuff.c | 43 ++++++++++++++++++++++++++++++++++++++
> 3 files changed, 51 insertions(+), 13 deletions(-)
>
> diff --git a/include/net/dropreason.h b/include/net/dropreason.h
> index 56cb7be92244..c157070b5303 100644
> --- a/include/net/dropreason.h
> +++ b/include/net/dropreason.h
> @@ -42,6 +42,11 @@ struct drop_reason_list {
> extern const struct drop_reason_list __rcu *
> drop_reasons_by_subsys[SKB_DROP_REASON_SUBSYS_NUM];
>
> +#ifdef CONFIG_TRACEPOINTS
> +const char *drop_reason_lookup(unsigned long long value);
> +void drop_reason_show(struct seq_file *m);
> +#endif
> +
> void drop_reasons_register_subsys(enum skb_drop_reason_subsys subsys,
> const struct drop_reason_list *list);
> void drop_reasons_unregister_subsys(enum skb_drop_reason_subsys subsys);
> diff --git a/include/trace/events/skb.h b/include/trace/events/skb.h
> index 07e0715628ec..8a1a63f9e796 100644
> --- a/include/trace/events/skb.h
> +++ b/include/trace/events/skb.h
> @@ -8,15 +8,9 @@
> #include <linux/skbuff.h>
> #include <linux/netdevice.h>
> #include <linux/tracepoint.h>
> +#include <net/dropreason.h>
>
> -#undef FN
> -#define FN(reason) TRACE_DEFINE_ENUM(SKB_DROP_REASON_##reason);
> -DEFINE_DROP_REASON(FN, FN)
> -
> -#undef FN
> -#undef FNe
> -#define FN(reason) { SKB_DROP_REASON_##reason, #reason },
> -#define FNe(reason) { SKB_DROP_REASON_##reason, #reason }
> +TRACE_DEFINE_SYM_FNS(drop_reason, drop_reason_lookup, drop_reason_show);
>
> /*
> * Tracepoint for free an sk_buff:
> @@ -44,13 +38,9 @@ TRACE_EVENT(kfree_skb,
>
> TP_printk("skbaddr=%p protocol=%u location=%pS reason: %s",
> __entry->skbaddr, __entry->protocol, __entry->location,
> - __print_symbolic(__entry->reason,
> - DEFINE_DROP_REASON(FN, FNe)))
> + __print_sym(__entry->reason, drop_reason ))
Minor nit: if you have to repost for other reasons, ^^ here
checkpatch complains for the extra space.
Otherwise LGTM,
Thanks!
Paolo
next prev parent reply other threads:[~2024-06-18 8:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-14 8:19 [PATCH v5 0/4] tracing: improve symbolic printing Johannes Berg
2024-06-14 8:19 ` [PATCH v5 1/4] tracing: add __print_sym() to replace __print_symbolic() Johannes Berg
2024-06-14 8:19 ` [PATCH v5 2/4] tracing/timer: use __print_sym() Johannes Berg
2024-06-14 8:19 ` [PATCH v5 3/4] net: dropreason: use new __print_sym() in tracing Johannes Berg
2024-06-18 8:26 ` Paolo Abeni [this message]
2024-06-14 8:19 ` [PATCH v5 4/4] net: drop_monitor: use drop_reason_lookup() Johannes Berg
2024-08-19 22:23 ` [PATCH v5 0/4] tracing: improve symbolic printing Steven Rostedt
2024-08-26 18:24 ` Johannes Berg
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=294c30a62d415c9b641be32df2b527cfff19ef62.camel@redhat.com \
--to=pabeni@redhat.com \
--cc=johannes.berg@intel.com \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.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).