From: Han Pingtian <phan@redhat.com>
To: linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org
Subject: [BUG] perf kmem: Processed 0 events and LOST 75691!
Date: Tue, 2 Aug 2011 11:59:14 +0800 [thread overview]
Message-ID: <20110802035914.GA6626@hpt.nay.redhat.com> (raw)
Hello,
I got this with 3.0 perf, but the running kernel is a old one:
[root@hp-dl580g7-01 perf]# ./perf kmem record sleep 1
[ perf record: Woken up 0 times to write data ]
[ perf record: Captured and wrote 21.789 MB perf.data (~951977 samples)
]
Processed 0 events and LOST 76148!
Check IO/CPU overload!
[root@hp-dl580g7-01 perf]# ./perf kmem stat
Processed 0 events and LOST 76148!
Check IO/CPU overload!
SUMMARY
=======
Total bytes requested: 5725028
Total bytes allocated: 6291512
Total bytes wasted on internal fragmentation: 566484
Internal fragmentation: 9.003941%
Cross CPU allocations: 28/84295
Is this a bug?
Thanks.
--
Han Pingtian
Quality Engineer
hpt @ #kernel-qe
Red Hat, Inc
Freedom ... courage ... Commitment ... ACCOUNTABILITY
reply other threads:[~2011-08-02 3:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20110802035914.GA6626@hpt.nay.redhat.com \
--to=phan@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--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).