From: "Frank Ch. Eigler" <fche@redhat.com>
To: Li Guanglei <guanglei@cn.ibm.com>
Cc: systemtap@sourceware.org
Subject: Re: Customization of LKET
Date: Fri, 02 Jun 2006 11:31:00 -0000 [thread overview]
Message-ID: <20060602113120.GC23361@redhat.com> (raw)
In-Reply-To: <447FAE49.6090900@cn.ibm.com>
Hi -
On Fri, Jun 02, 2006 at 11:19:37AM +0800, Li Guanglei wrote:
> [...]
> But I have to confess that it seems a waste to introduce such a new
> function into systemtap's translator. It seems too application
> specific. A more generic trace facilities at script level is more
> meaningful.
That's what I was thinking.
> Before we find the final solution, I think I can use a temp solution [...]
It's worth the try.
> I am thinking of revert my changes of lket_trace_extra() to
> translator.
Sure.
> >[...] The overall size of the context structure may be small
> >enough even with a quadrupled MAXSTRINGLEN for it to work out fine.
> >Test it and see.
>
> I tested using a simple script:
Thank you!
> [...] it shows that the size of context will increase from 6608 to
> 51408 if MAXSTRINGLEN is defined as 1024. Seems acceptable, right?
My understanding is that a number below 64K is fine. I expect that we
can have another round of context size reduction with translator
improvements. One possibility is to have it detect absence of
recursion, to let it compute a minimal MAXNESTING parameter.
- FChE
next prev parent reply other threads:[~2006-06-02 11:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-30 14:38 Li Guanglei
2006-05-31 7:49 ` Li Guanglei
2006-06-01 23:22 ` Frank Ch. Eigler
2006-06-02 3:19 ` Li Guanglei
2006-06-02 11:31 ` Frank Ch. Eigler [this message]
2006-06-07 2:00 ` Li Guanglei
2006-06-08 16:04 ` Frank Ch. Eigler
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=20060602113120.GC23361@redhat.com \
--to=fche@redhat.com \
--cc=guanglei@cn.ibm.com \
--cc=systemtap@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).