From: Ingo Molnar <mingo@elte.hu>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Frederic Weisbecker <fweisbec@gmail.com>,
Steven Rostedt <rostedt@goodmis.org>,
Zhaolei <zhaolei@cn.fujitsu.com>,
Tom Zanussi <tzanussi@gmail.com>, Li Zefan <lizf@cn.fujitsu.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] tracing/lockdep: turn lock->name into an array
Date: Tue, 14 Apr 2009 12:27:54 +0200 [thread overview]
Message-ID: <20090414102754.GH3558@elte.hu> (raw)
In-Reply-To: <1239695296.21985.6725.camel@twins>
* Peter Zijlstra <peterz@infradead.org> wrote:
> On Tue, 2009-04-14 at 00:42 +0200, Frederic Weisbecker wrote:
> > > +#define LOCK_NAME_SIZE 25
> >
> >
> >
> > This constant may look a bit weird.
> > I just started with the assumption that a full lock name
> > will rarely exceed this length.
> >
> > If you agree with it, I will expand the conversion of lockdep
> > TRACE_FORMAT to TRACE_EVENTS with the same assumption.
> > So that we will be able to use filters with locks events.
>
> I really really hate this.
>
> if you pick a size on the top end so that all lock->name's fit in,
> you're wasting heaps of space, if you pick a median length,
> everything will get truncated.
>
> If you're going to do a copy, just do the print into the buffer by
> using _FORMAT and be done with it.
what i suggested was a variable length field. That solves the size
issue. The ring-buffer supports variable size records anyway.
Ingo
next prev parent reply other threads:[~2009-04-14 10:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-13 22:36 [PATCH] tracing/lockdep: turn lock->name into an array Frederic Weisbecker
2009-04-13 22:42 ` Frederic Weisbecker
2009-04-13 22:58 ` Ingo Molnar
2009-04-14 7:48 ` Peter Zijlstra
2009-04-14 10:27 ` Ingo Molnar [this message]
2009-04-14 21:22 ` Frederic Weisbecker
2009-04-13 23:01 ` Ingo Molnar
2009-04-14 0:24 ` Frederic Weisbecker
2009-04-14 6:35 ` KOSAKI Motohiro
2009-04-14 6:53 ` Ingo Molnar
2009-04-14 6:56 ` KOSAKI Motohiro
2009-04-14 7:20 ` Peter Zijlstra
2009-04-14 10:25 ` Ingo Molnar
2009-04-17 17:25 ` Jeremy Fitzhardinge
2009-04-17 17:27 ` Peter Zijlstra
2009-04-17 17:36 ` Steven Rostedt
2009-04-17 20:29 ` Frederic Weisbecker
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=20090414102754.GH3558@elte.hu \
--to=mingo@elte.hu \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tzanussi@gmail.com \
--cc=zhaolei@cn.fujitsu.com \
/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