All of lore.kernel.org
 help / color / mirror / Atom feed
From: Frederic Weisbecker <fweisbec@gmail.com>
To: Li Zefan <lizf@cn.fujitsu.com>
Cc: Ingo Molnar <mingo@elte.hu>, Steven Rostedt <rostedt@goodmis.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] tracing/events: change the type of __str_loc_item to unsigned short
Date: Sun, 24 May 2009 22:31:51 +0200	[thread overview]
Message-ID: <20090524203148.GA6471@nowhere> (raw)
In-Reply-To: <4A14EDB6.2050507@cn.fujitsu.com>

On Thu, May 21, 2009 at 01:59:18PM +0800, Li Zefan wrote:
> When defining a dynamic size string, we add __str_loc_##item to the
> trace entry, and it stores the location of the actual string in
> entry->_str_data[]
> 
> 'unsigned short' should be sufficient to store this information, thus
> we save 2 bytes per dyn-size string in the ring buffer.
> 
> [ Impact: reduce memory occupied by dyn-size strings in ring buffer ]
> 
> Signed-off-by: Li Zefan <lizf@cn.fujitsu.com>
> ---
>  include/trace/ftrace.h |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
> 
> diff --git a/include/trace/ftrace.h b/include/trace/ftrace.h
> index edb02bc..b5ff2e8 100644
> --- a/include/trace/ftrace.h
> +++ b/include/trace/ftrace.h
> @@ -25,7 +25,7 @@
>  #define __field(type, item)		type	item;
>  
>  #undef __string
> -#define __string(item, src)		int	__str_loc_##item;
> +#define __string(item, src)		unsigned short	__str_loc_##item;
>  
>  #undef TP_STRUCT__entry
>  #define TP_STRUCT__entry(args...) args
> -- 1.5.4.rc3 


Yeah, a max length of about 32000 is sufficient, the filter
engine is bounded to MAX_FILTER_STR_VAL anyway :)

Acked-by: Frederic Weisbecker <fweisbec@gmail.com>


  reply	other threads:[~2009-05-24 20:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-21  5:59 [PATCH] tracing/events: change the type of __str_loc_item to unsigned short Li Zefan
2009-05-24 20:31 ` Frederic Weisbecker [this message]
2009-05-27 22:34 ` [tip:tracing/core] " tip-bot for Li Zefan

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=20090524203148.GA6471@nowhere \
    --to=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lizf@cn.fujitsu.com \
    --cc=mingo@elte.hu \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.