From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Pavel Odintsov <pavel.odintsov@gmail.com>
Cc: linux-kernel@vger.kernel.org, David Ahern <dsahern@gmail.com>
Subject: Re: [PATCH 0/7] [RFC] kernel: add a netlink interface to get information about processes
Date: Fri, 27 Feb 2015 17:43:46 -0300 [thread overview]
Message-ID: <20150227204346.GB28401@kernel.org> (raw)
In-Reply-To: <CALgsdbdH4c-JXTWNcgHDFHRLUM_ff=_UxSvj9c1VhWHCfbR-pA@mail.gmail.com>
Em Thu, Feb 19, 2015 at 05:00:12PM +0400, Pavel Odintsov escreveu:
> Hello!
>
> In addition to my post I want to mention another issue related with
> slow /proc read in perf toolkit. On my server with 25 000 processes I
> need about ~15 minutes for loading perf top toolkit completely.
>
> https://bugzilla.kernel.org/show_bug.cgi?id=86991
Right, one way would be to, in the 'perf top' case to defer getting
thread information to when we need it, i.e. when we get a sample for a
pid that we have no struct thread associated with.
We would speed up 'perf top' startup but would introduce jitter down the
line, and would be up for races, but hey, we already are, using /proc
:-/
But that would not work for 'perf record', as we need to in advance
generate those records as we don't do any processing of samples...
Yeah, for preexisting threads we do have a problem since day one, what
we use is just what can be done with existing stuff.
I saw that there were some more messages in this thread, its just that I
haven't found them in my mailbox when David Ahern pointed this out this
discussion to me :-\
>From the subject line, there is patchkit, but I couldn't find it... Can
you resend it to me or point me to some url where I can get it?
- Arnaldo
next prev parent reply other threads:[~2015-02-27 20:43 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-19 13:00 [PATCH 0/7] [RFC] kernel: add a netlink interface to get information about processes Pavel Odintsov
2015-02-27 20:43 ` Arnaldo Carvalho de Melo [this message]
2015-02-27 20:54 ` David Ahern
2015-02-27 21:50 ` Arnaldo Carvalho de Melo
-- strict thread matches above, loose matches on Subject: below --
2015-02-19 12:50 Pavel Odintsov
2015-02-17 8:20 Andrey Vagin
2015-02-17 8:53 ` Arnd Bergmann
2015-02-17 21:33 ` Andrew Vagin
2015-02-18 11:06 ` Arnd Bergmann
2015-02-18 12:42 ` Andrew Vagin
2015-02-18 14:46 ` Arnd Bergmann
2015-02-19 14:04 ` Andrew Vagin
2015-02-17 16:09 ` David Ahern
2015-02-17 20:32 ` Andrew Vagin
2015-02-17 19:05 ` Andy Lutomirski
2015-02-18 14:27 ` Andrew Vagin
2015-02-19 1:18 ` Andy Lutomirski
2015-02-19 21:39 ` Andrew Vagin
2015-02-20 20:33 ` Andy Lutomirski
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=20150227204346.GB28401@kernel.org \
--to=acme@kernel.org \
--cc=dsahern@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel.odintsov@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