From: Matt Fleming <matt@console-pimps.org>
To: linux-ia64@vger.kernel.org
Subject: Re: How performance critical is fsys_rt_sigprocmask()?
Date: Wed, 24 Aug 2011 19:51:31 +0000 [thread overview]
Message-ID: <1314215491.3611.49.camel@mfleming-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <1314196796.3611.38.camel@mfleming-mobl1.ger.corp.intel.com>
On Wed, 2011-08-24 at 09:13 -0600, David Mosberger-Tang wrote:
> Matt,
>
> As I remember it, it was the single system-call on the critical path of
> libunwind. Don't remember the numbers, but it was significant.
Interesting. So that'd be the critical path for things like performance
analysis tools that record stack traces? Yeah, I can see how you'd want
the stack trace recording to have very little overhead.
I guess I'll start writing ia64 assembly then...
--
Matt Fleming, Intel Open Source Technology Center
prev parent reply other threads:[~2011-08-24 19:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-24 14:39 How performance critical is fsys_rt_sigprocmask()? Matt Fleming
2011-08-24 19:51 ` Matt Fleming [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=1314215491.3611.49.camel@mfleming-mobl1.ger.corp.intel.com \
--to=matt@console-pimps.org \
--cc=linux-ia64@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