From: Han Pingtian <phan@redhat.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: linux-kernel@vger.kernel.org, Arnaldo Carvalho de Melo <acme@redhat.com>
Subject: Re: [BUG] perf failed on multi-cpus system with multi-events specified
Date: Wed, 2 Mar 2011 18:12:53 +0800 [thread overview]
Message-ID: <20110302101253.GA12300@hpt.nay.redhat.com> (raw)
In-Reply-To: <1299058716.2428.13473.camel@twins>
On Wed, Mar 02, 2011 at 10:38:36AM +0100, Peter Zijlstra wrote:
> On Wed, 2011-03-02 at 11:58 +0800, Han Pingtian wrote:
> > Error: sys_perf_event_open() syscall returned with -1 (Too many open
> > files). /bin/dmesg may provide additional information.
>
> Well, you tried to use 42 events (quick count), we need to open a fd for
> each cpu for each event, which results in 1008 fds, which together with
> some actual file handles might have tickled your fd limit.
Got it. Thanks.
--
Han Pingtian
Quality Engineer
hpt @ #kernel-qe
Red Hat, Inc
Freedom ... courage ... Commitment ... ACCOUNTABILITY
prev parent reply other threads:[~2011-03-02 10:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-02 3:58 Han Pingtian
2011-03-02 4:35 ` Eric Dumazet
2011-03-02 6:32 ` Han Pingtian
2011-03-02 9:38 ` Peter Zijlstra
2011-03-02 10:12 ` Han Pingtian [this message]
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=20110302101253.GA12300@hpt.nay.redhat.com \
--to=phan@redhat.com \
--cc=acme@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.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
all inboxes | Powered by JetHome®