From: Dave Jones <davej@redhat.com>
To: Vince Weaver <vincent.weaver@maine.edu>
Cc: Tommi Rantala <tt.rantala@gmail.com>, trinity@vger.kernel.org
Subject: Re: [patch] perf_event_open enable sysfs exported events
Date: Wed, 19 Jun 2013 12:38:41 -0400 [thread overview]
Message-ID: <20130619163841.GA22483@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1306191232170.27743@vincent-weaver-1.um.maine.edu>
On Wed, Jun 19, 2013 at 12:34:43PM -0400, Vince Weaver wrote:
> On Wed, 19 Jun 2013, Dave Jones wrote:
>
> > On Thu, Jun 13, 2013 at 03:58:37PM -0400, Vince Weaver wrote:
> > > On Thu, 13 Jun 2013, Tommi Rantala wrote:
> > >
> > > > Unable to opendir /sys/bus/event_source/devices : Resource temporarily
> > > > unavailable
> > >
> > > Though in the case where /sys/bus/event_source/devices isn't available
> > > trinity will try opening it again each time it tries to do a
> > > PERF_TYPE_READ_FROM_SYSFS type (1 time in 7). Not sure if it's
> > > worth rate-limiting that.
> >
> > I'm puzzled why I'm seeing opendir() fail with -ENOMEM when there's gigabytes
> > of free memory available. Likewise, getting -EAGAIN seems.. weird.
>
> Is this easy to reproduce? I haven't seen it locally but then again
> I have only been running trinity with -c perf_event_open
> I only left the debug message in because I thought it would be unusual
> for a quick sysfs traversal to fail.
Hmm, that's weird. When I run with -c perf_event_open it doesn't happen.
So it's an interaction with something else that's causing it. Fun.
> > init_pmus might be simpler if it was converted to use nftw() too.
>
> I was unaware of the existence of nftw(), I'll work on updating the code
> to use it.
I only recently learned of it myself. the tree walking in files.c got
a lot simpler. See b0d4df18a6785b0c3347f521bb2c09e88b0c0966.
Dave
next prev parent reply other threads:[~2013-06-19 16:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-11 4:33 [patch] perf_event_open enable sysfs exported events Vince Weaver
2013-06-11 21:05 ` Dave Jones
2013-06-11 21:24 ` Vince Weaver
2013-06-11 21:32 ` Dave Jones
2013-06-11 22:21 ` Vince Weaver
2013-06-11 22:25 ` Dave Jones
2013-06-13 19:38 ` Tommi Rantala
2013-06-13 19:58 ` Vince Weaver
2013-06-13 20:53 ` Dave Jones
2013-06-13 21:07 ` Vince Weaver
2013-06-13 21:05 ` Dave Jones
2013-06-19 15:27 ` Dave Jones
2013-06-19 16:34 ` Vince Weaver
2013-06-19 16:38 ` Dave Jones [this message]
2013-06-19 19:29 ` Vince Weaver
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=20130619163841.GA22483@redhat.com \
--to=davej@redhat.com \
--cc=trinity@vger.kernel.org \
--cc=tt.rantala@gmail.com \
--cc=vincent.weaver@maine.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.