From: Christopher Smith <x@xman.org>
To: "Carey B. Stortz" <castortz@nmu.edu>, linux-kernel@vger.kernel.org
Subject: Re: Signal Handling Performance?
Date: Wed, 04 Apr 2001 18:41:10 -0700 [thread overview]
Message-ID: <50490000.986434870@hellman> (raw)
In-Reply-To: <5.0.0.25.2.20010404211904.009d3eb0@pop.mail.nmu.edu>
--On Wednesday, April 04, 2001 21:30:51 -0400 "Carey B. Stortz"
<castortz@nmu.edu> wrote:
> either stayed the same or had a performance increase. A general decrease
> started around kernel 2.1.32, then performance drastically fell at kernel
> 2.3.20. There is an Excel graph which shows the trend at:
>
> http://euclid.nmu.edu/~benchmark/Carey/signalhandling.gif
>
> I was wondering if anybody had any ideas why this is happening, and what
> happened in kernel 2.3.20 to cause such a decrease in performance?
Lies, damn lies, and benchmarks. ;-) Seriously though, I'm not clear on
what you are measuring or how you are measuring it. It looks like this is
measuring signal latency, which is important, but what about thoroughput?
--Chris
prev parent reply other threads:[~2001-04-05 1:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-05 1:30 Signal Handling Performance? Carey B. Stortz
2001-04-05 1:41 ` Christopher Smith [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=50490000.986434870@hellman \
--to=x@xman.org \
--cc=castortz@nmu.edu \
--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