From: Grant Grundler <grundler@parisc-linux.org>
To: Tres Melton <tres@mindspring.com>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] [Testers wanted] New glibc with profiling fixed.
Date: Sun, 24 Jul 2005 18:09:19 -0600 [thread overview]
Message-ID: <20050725000919.GA18659@colo.lackof.org> (raw)
In-Reply-To: <1122036994.10454.131.camel@thor.tres.org>
On Fri, Jul 22, 2005 at 06:56:34AM -0600, Tres Melton wrote:
> | Here's "apps/openssl speed rsa" gprof output from my c3000.
> | (2.6.0-pa7, Debian testing)
> |
> | TBH, it looks wrong.
>
> It is wrong. For details please see:
>
> http://bugs.gentoo.org/show_bug.cgi?id=90090
Ugh. user space vs kernel space HZ battles.
> If you have any more information on the subject
Sorry - I really don't.
I'm happy to run more tests on kernel patches if that would help.
> I would appreciate it
> as a number of us are preparing to take this issue to the LKML. I'm
> specifically looking at a convincing reason to put forth to Linus to
> export the correct clock-ticks/second. Linus has stated in the past
> that user space has no need for the information. A couple of other
> kernel devs are going to back me up here but we need a good argument to
> get Linus to change his mind.
I'm certainly not the one who has a solid grasp of the problem.
I just recognized the output looked wrong.
Another kernel developer has suggested this is a gprof bug.
I was told the kernel has two types of ticks: one for kernel and another
for users space - some conversation needs to take place by gprof
that I know nothing about.
thanks,
grant
_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
next prev parent reply other threads:[~2005-07-25 0:09 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-22 12:56 [parisc-linux] [Testers wanted] New glibc with profiling fixed Tres Melton
2005-07-25 0:09 ` Grant Grundler [this message]
[not found] ` <1122272788.10644.71.camel@thor.tres.org>
2005-07-26 13:24 ` Grant Grundler
2005-07-26 13:37 ` Tres Melton
2005-07-26 14:18 ` Matthew Wilcox
2005-07-26 14:25 ` Randolph Chung
2005-07-26 17:01 ` Carlos O'Donell
2005-07-26 17:09 ` Matthew Wilcox
2005-07-26 18:08 ` Carlos O'Donell
2005-07-26 15:26 ` Tres Melton
2005-07-26 17:16 ` Carlos O'Donell
[not found] <no.id>
2004-01-07 21:14 ` John David Anglin
2004-01-07 21:14 ` John David Anglin
-- strict thread matches above, loose matches on Subject: below --
2004-01-05 19:48 Carlos O'Donell
2004-01-05 19:48 Carlos O'Donell
2004-01-05 19:48 ` Carlos O'Donell
2004-01-05 19:48 ` Carlos O'Donell
2004-01-11 4:09 ` Grant Grundler
2004-01-11 20:43 ` Carlos O'Donell
2004-01-11 20:43 ` Carlos O'Donell
2004-01-12 16:38 ` Grant Grundler
2004-01-12 16:38 ` Grant Grundler
2004-01-13 5:42 ` Grant Grundler
2004-01-13 5:42 ` Grant Grundler
2004-01-13 8:46 ` Joel Soete
2004-01-13 8:46 ` Joel Soete
2004-01-11 4:09 ` Grant Grundler
2004-01-05 20:45 ` Grant Grundler
2004-01-05 22:00 ` Carlos O'Donell
2004-01-05 22:00 ` Carlos O'Donell
2004-01-05 20:45 ` Grant Grundler
2004-01-07 21:04 ` John David Anglin
2004-01-07 21:04 ` John David Anglin
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=20050725000919.GA18659@colo.lackof.org \
--to=grundler@parisc-linux.org \
--cc=parisc-linux@lists.parisc-linux.org \
--cc=tres@mindspring.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