public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "jistone at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug kprobes/10839] kretprobes use excessive memory on x86_64 rawhide
Date: Mon, 26 Oct 2009 23:14:00 -0000	[thread overview]
Message-ID: <20091026231405.26651.qmail@sourceware.org> (raw)
In-Reply-To: <20091024022959.10839.jistone@redhat.com>


------- Additional Comments From jistone at redhat dot com  2009-10-26 23:14 -------
(In reply to comment #2)
> That's 37MB for a change of 100 maxactive, which comes to about 136 bytes each.

This waste is because kretprobes allocates each instance with a separate
kmalloc, which usually allocates more than actually requested.

  global waste
  probe kernel.trace("kmalloc") {
    waste <<< ($bytes_alloc - $bytes_req)
  }
  probe timer.s(1) {
    if (@count(waste))
      printdln(" ", @count(waste), @sum(waste), @avg(waste))
    delete waste
  }

During KRETACTIVE=100, I get:
  271 21949 80
  281281 27015907 96
  141 13280 94

During KRETACTIVE=200, I get:
  25 2664 106
  561746 53935824 96
  127 12264 96

-- 


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

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

  parent reply	other threads:[~2009-10-26 23:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-24  2:30 [Bug kprobes/10839] New: " jistone at redhat dot com
2009-10-25  8:01 ` [Bug kprobes/10839] " fche at redhat dot com
2009-10-26 23:07 ` jistone at redhat dot com
2009-10-26 23:14 ` jistone at redhat dot com [this message]
2009-10-29 17:02 ` [Bug translator/10839] KRETACTIVE should have a smaller default value jistone at redhat dot com
2009-10-30 12:12 ` fche at redhat dot com
2009-10-30 22:50 ` jistone 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=20091026231405.26651.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).