mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tom Zanussi <zanussi@kernel.org>
To: Artem Bityutskiy <dedekind1@gmail.com>,
	Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tracing: synth events: increase max fields count
Date: Thu, 02 Sep 2021 15:54:34 -0500	[thread overview]
Message-ID: <df073c9f719a7da37a68148ea51aa28d06a14e40.camel@kernel.org> (raw)
In-Reply-To: <20210901135513.3087062-1-dedekind1@gmail.com>

Hi Artem,

On Wed, 2021-09-01 at 16:55 +0300, Artem Bityutskiy wrote:
> From: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>
> 
> Sometimes it is useful to construct larger synthetic trace events.
> Increase
> 'SYNTH_FIELDS_MAX' (maximum number of fields in a synthetic event)
> from 32 to
> 64.
> 
> Signed-off-by: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>
> ---
>  kernel/trace/trace_synth.h | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/kernel/trace/trace_synth.h b/kernel/trace/trace_synth.h
> index 4007fe95cf42..b29595fe3ac5 100644
> --- a/kernel/trace/trace_synth.h
> +++ b/kernel/trace/trace_synth.h
> @@ -5,7 +5,7 @@
>  #include "trace_dynevent.h"
>  
>  #define SYNTH_SYSTEM		"synthetic"
> -#define SYNTH_FIELDS_MAX	32
> +#define SYNTH_FIELDS_MAX	64
>  
>  #define STR_VAR_LEN_MAX		MAX_FILTER_STR_VAL /* must be
> multiple of sizeof(u64) */
>  

This looks fine, but it does also bloat the arrays that use it as a
size.  There's only one that I'd be worried about, the per-elt
hist_elt_data[] array, but I'll send a patch shortly that gets rid of
that limitation.

Acked-by: Tom Zanussi <zanussi@kernel.org>

Thanks!

Tom


      reply	other threads:[~2021-09-02 20:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-01 13:55 Artem Bityutskiy
2021-09-02 20:54 ` Tom Zanussi [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=df073c9f719a7da37a68148ea51aa28d06a14e40.camel@kernel.org \
    --to=zanussi@kernel.org \
    --cc=dedekind1@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rostedt@goodmis.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

all inboxes | Powered by JetHome®