From: Matt Fleming <matt@console-pimps.org>
To: linux-ia64@vger.kernel.org
Subject: How performance critical is fsys_rt_sigprocmask()?
Date: Wed, 24 Aug 2011 14:39:56 +0000 [thread overview]
Message-ID: <1314196796.3611.38.camel@mfleming-mobl1.ger.corp.intel.com> (raw)
Hi,
I'm looking at the code code in fsys_rt_sigprocmask() and I'm wondering
whether it really needs to be implemented in assembly. I recently posted
a patch series that converted code modifying current->blocked to use the
new set_current_blocked() helper but initially missed the code in
fsys_rt_sigprocmask() because it's not written in C.
It seems this sort of thing has happened before too, e.g. with the
ticket lock implementation as seen in commit f574c8431917 ("[IA64] fix
siglock"), presumably for the same reasons.
So I was wondering, from a code maintenance perspective, would it make
sense to delete the custom implementation of sys_rt_sigprocmask() and
use the generic one? Or does that function genuinely have a need to be
written in hand-optimised assembly?
--
Matt Fleming, Intel Open Source Technology Center
next reply other threads:[~2011-08-24 14:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-24 14:39 Matt Fleming [this message]
2011-08-24 19:51 ` How performance critical is fsys_rt_sigprocmask()? Matt Fleming
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=1314196796.3611.38.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