From: "dsmith at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug runtime/22265] on rawhide, we're getting a kernel panic
Date: Mon, 09 Oct 2017 19:19:00 -0000 [thread overview]
Message-ID: <bug-22265-6586-fiFH5BTevC@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-22265-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=22265
--- Comment #3 from David Smith <dsmith at redhat dot com> ---
(In reply to David Smith from comment #2)
> I wonder if the bpf changes
> have upped our memory requirements.
Here's the pre-bpf code on this rawhide system:
====
# ./stap -vwp2 -e 'probe kernel.function("*") {} probe
module("*").function("*") {} probe kernel.function("*").call {} probe
module("*").function("*").call {} probe kernel.function("*").return {} probe
module("*").function("*").return {} probe kernel.function("*").inline {} probe
module("*").function("*").inline {}' > /dev/null
Pass 1: parsed user script and 467 library scripts using
143236virt/47356res/8128shr/39336data kb, in 120usr/30sys/147real ms.
Pass 2: analyzed script: 2100235 probes, 0 functions, 0 embeds, 0 globals using
4998228virt/3816824res/1660shr/4894328data kb, in 73530usr/9430sys/122315real
ms.
====
Here's the current HEAD code on the same system:
====
# /usr/local/bin/stap -vwp2 -e 'probe kernel.function("*") {} probe
module("*").function("*") {} probe kernel.function("*").call {} probe
module("*").function("*").call {} probe kernel.function("*").return {} probe
module("*").function("*").return {} probe kernel.function("*").inline {} probe
module("*").function("*").inline {}' > /dev/null
Pass 1: parsed user script and 469 library scripts using
143748virt/47616res/7852shr/39692data kb, in 130usr/30sys/470real ms.
Pass 2: analyzed script: 2100235 probes, 0 functions, 0 embeds, 0 globals using
5031620virt/3829572res/1592shr/4927564data kb, in 70740usr/9160sys/109159real
ms.
====
So, in pass 2 we've gone from:
virt: 4998228 -> 5031620
res: 3816824 -> 3829572
shr: 1660 -> 1592
data: 4894328 -> 4927564
So, the memory use has been upped a bit, but nothing dramatic.
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2017-10-09 19:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-05 16:10 [Bug runtime/22265] New: " dsmith at redhat dot com
2017-10-06 20:45 ` [Bug runtime/22265] " dsmith at redhat dot com
2017-10-09 13:39 ` dsmith at redhat dot com
2017-10-09 19:19 ` dsmith at redhat dot com [this message]
2020-02-19 21:39 ` 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=bug-22265-6586-fiFH5BTevC@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--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).