From: William Cohen <wcohen@redhat.com>
To: David Ahern <dsahern@gmail.com>,
"linux-perf-use." <linux-perf-users@vger.kernel.org>
Cc: 大平怜 <rei.odaira@gmail.com>,
oprofile-list <oprofile-list@lists.sourceforge.net>
Subject: Re: Issue perf attaching to processes creating many short-live threads
Date: Fri, 23 Oct 2015 15:27:04 -0400 [thread overview]
Message-ID: <562A8A08.9010101@redhat.com> (raw)
In-Reply-To: <562A82F5.8090306@gmail.com>
On 10/23/2015 02:56 PM, David Ahern wrote:
> On 10/23/15 12:52 PM, William Cohen wrote:
>> Earlier this month Rei Odeira found that the oprofile tool operf would
>> have problems attaching and monitoring a process that created many
>> very short-lived threads. It looks like the kernel's perf tool also
>> has issues when attempting to attach and monitor a process that is
>> creating many short-lived threads.
>
> known a problem. If this is the problem I think it is you will find that strace shows perf stuck walking /proc directory.
>
> David
>
Hi David,
Is the following thread related to the problem?
[PATCH 1/1] perf,tools: add time out to force stop endless mmap processing"
http://lkml.iu.edu/hypermail/linux/kernel/1506.1/02251.html
Or is there some other thread about the problem?
-Will
next prev parent reply other threads:[~2015-10-23 19:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-23 18:52 Issue perf attaching to processes creating many short-live threads William Cohen
2015-10-23 18:56 ` David Ahern
2015-10-23 19:27 ` William Cohen [this message]
2015-10-23 19:35 ` David Ahern
2015-10-26 19:49 ` Arnaldo Carvalho de Melo
2015-10-26 21:42 ` David Ahern
2015-10-27 12:33 ` Arnaldo Carvalho de Melo
2015-10-27 14:15 ` David Ahern
2015-10-27 14:47 ` 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=562A8A08.9010101@redhat.com \
--to=wcohen@redhat.com \
--cc=dsahern@gmail.com \
--cc=linux-perf-users@vger.kernel.org \
--cc=oprofile-list@lists.sourceforge.net \
--cc=rei.odaira@gmail.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 NNTP newsgroup(s).