public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug translator/5673] tweak kprobe config arrays
Date: Sat, 26 Jan 2008 03:16:00 -0000	[thread overview]
Message-ID: <20080126031557.9893.qmail@sourceware.org> (raw)
In-Reply-To: <20080125184406.5673.fche@redhat.com>


------- Additional Comments From fche at redhat dot com  2008-01-26 03:15 -------
Some initial findings on the 'probe kernel.function("*") {}' .ko:

Of the .ko space, 90%+ of the data is the stap_dwarf_probe[]
array.  On x86-64, each entry is 200 bytes long, of which
an embedded blank "struct kprobe" is 120, and the union
"struct kretprobe" is 152.  These latter structs need some
independent runtime existence but they don't have to live in
initialized data ==> dynamically allocate them during module_init.

Next, the probe point string, averages ~30 bytes per probe, is
stored in .rodata.str but is not directly compressible.  Perhaps
it is worthwhile breaking up this string field so that link-time
duplicate elimination can work.  Substrings like `kernel.function("'
or `@file/foo.c' could be merged.  (This would mean making the
stap_dwarf_probe struct contain a small array of char*'s instead
of just one.)

Doing these two things should reduce the unnecessary bloat in the
.ko file considerably.  It should no longer be 93%-compressible by
gzip.


-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|tewak kprobe config arrays  |tweak kprobe config arrays


http://sourceware.org/bugzilla/show_bug.cgi?id=5673

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

  reply	other threads:[~2008-01-26  3:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-25 18:44 [Bug translator/5673] New: tewak " fche at redhat dot com
2008-01-26  3:16 ` fche at redhat dot com [this message]
2008-01-26 16:57 ` [Bug translator/5673] tweak " fche at redhat dot com

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=20080126031557.9893.qmail@sourceware.org \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=systemtap@sources.redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).