From: Chris Friesen <cfriesen@nortelnetworks.com>
To: Linux kernel <linux-kernel@vger.kernel.org>
Subject: 2.4.18-2.4.22 signal handling speed regression
Date: Fri, 26 Mar 2004 15:06:05 -0500 [thread overview]
Message-ID: <40648D2D.2000201@nortelnetworks.com> (raw)
We have an app that uses signals heavily (30K/sec at times). When
moving it from 2.4.18 to 2.4.22, we noticed a significant speed
decrease, to the point where it is about 2.5 times slower on 2.4.22.
We're trying to figure out what is causing the problem, but I thought
I'd see if anyone has any ideas off the top of their heads.
PowerPC hardware, 1 cpu, single-threaded app.
Thanks,
Chris
reply other threads:[~2004-03-26 20:06 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=40648D2D.2000201@nortelnetworks.com \
--to=cfriesen@nortelnetworks.com \
--cc=linux-kernel@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