linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rick Jones <rick.jones2@hp.com>
To: linux-perf-users@vger.kernel.org
Subject: Memory leak in 3.17.rc6.g09bba1?
Date: Thu, 13 Nov 2014 17:28:15 -0800	[thread overview]
Message-ID: <54655AAF.90604@hp.com> (raw)

I am running a command:

perf top -a -g -e skb:kfree_skb

on a laptop running a 3.18.0-rc2+ kernel from davem's net-next tree. 
While that is running I hit the system as the target of a netperf TCP_CC 
test (ie netserver is running on the system where perf is running, and 
netperf is run on another system, pointing at the first).  I then expand 
the kfree_skb() line and the sk_stream_kill_queues  and 
tcp_rcv_state_process lines "within" that expansion.

If I watch with plain "top" in another window I can see the RES value 
for the perf process steadily increasing and also its CPU utlization. 
The latter finally peaks at 100% (this is a core 2 duo laptop).

After about 1800 seconds of being the target of a netperf TCP_CC test 
the RES value for the perf utility is over 1G.

If I wait long enough, perf will finally segfault.

Is this a known issue?  If I should file a more formal bug report 
somewhere let me know.

happy benchmarking,

rick jones

raj@raj-8510w:~$ net-next/tools/perf/perf --version
perf version 3.17.rc6.g09bba1

netperf -t tcp_cc -H <perfsystem> -l 3600

might need to repeat it a few times to get the segfault?

             reply	other threads:[~2014-11-14  1:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-14  1:28 Rick Jones [this message]
2014-11-14 12:30 ` Memory leak in 3.17.rc6.g09bba1? Arnaldo Carvalho de Melo

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=54655AAF.90604@hp.com \
    --to=rick.jones2@hp.com \
    --cc=linux-perf-users@vger.kernel.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 NNTP newsgroup(s).