From: Steven Rostedt <rostedt@goodmis.org>
To: David Ahern <dsahern@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
"David S. Miller" <davem@davemloft.net>,
netdev@vger.kernel.org
Subject: Re: [PATCH] tracing/ipv4/ipv6: Give size to name field in fib*_lookup_table event
Date: Sun, 3 Jul 2022 19:16:54 -0400 [thread overview]
Message-ID: <20220703191654.082db731@gandalf.local.home> (raw)
In-Reply-To: <5f25dd4a-7394-cf97-4fc8-c43f0c449fc7@gmail.com>
On Sun, 3 Jul 2022 13:03:20 -0600
David Ahern <dsahern@gmail.com> wrote:
> > Alternatively, if the intent was to use a fixed size, then it should be
> > converted into __array() of type char, which will remove the meta data in
> > the event that stores the size.
>
> I would prefer this option over duplicating the all of the checks to
> save 14B.
That's why I mentioned the alternative. To give you that option.
I'll send a v2 later that uses the static array.
-- Steve
prev parent reply other threads:[~2022-07-03 23:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-03 14:23 [PATCH] tracing/ipv4/ipv6: Give size to name field in fib*_lookup_table event Steven Rostedt
2022-07-03 19:03 ` David Ahern
2022-07-03 23:16 ` Steven Rostedt [this message]
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=20220703191654.082db731@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=davem@davemloft.net \
--cc=dsahern@gmail.com \
--cc=linux-kernel@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