From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <systemtap-return-25646-listarch-systemtap=sources.redhat.com@sourceware.org>
Received: (qmail 35736 invoked by alias); 9 Oct 2017 19:19:00 -0000
Mailing-List: contact systemtap-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <systemtap.sourceware.org>
List-Subscribe: <mailto:systemtap-subscribe@sourceware.org>
List-Post: <mailto:systemtap@sourceware.org>
List-Help: <mailto:systemtap-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: systemtap-owner@sourceware.org
Received: (qmail 35616 invoked by uid 48); 9 Oct 2017 19:18:55 -0000
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
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: systemtap
X-Bugzilla-Component: runtime
X-Bugzilla-Version: unspecified
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dsmith at redhat dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: systemtap at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-22265-6586-fiFH5BTevC@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-22265-6586@http.sourceware.org/bugzilla/>
References: <bug-22265-6586@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2017-q4/txt/msg00020.txt.bz2

https://sourceware.org/bugzilla/show_bug.cgi?id=3D22265

--- 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:

=3D=3D=3D=3D
# ./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 {} pr=
obe
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 u=
sing
4998228virt/3816824res/1660shr/4894328data kb, in 73530usr/9430sys/122315re=
al
ms.
=3D=3D=3D=3D

Here's the current HEAD code on the same system:

=3D=3D=3D=3D
# /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 {} pr=
obe
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 u=
sing
5031620virt/3829572res/1592shr/4927564data kb, in 70740usr/9160sys/109159re=
al
ms.
=3D=3D=3D=3D

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.

--=20
You are receiving this mail because:
You are the assignee for the bug.