public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Con Kolivas <kernel@kolivas.org>
To: Giuliano Pochini <pochini@shiny.it>
Cc: linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: [BENCHMARK] 100Hz v 1000Hz with contest
Date: Tue, 3 Jun 2003 20:36:49 +1000	[thread overview]
Message-ID: <200306032036.49790.kernel@kolivas.org> (raw)
In-Reply-To: <XFMail.20030603100038.pochini@shiny.it>

On Tue, 3 Jun 2003 18:00, Giuliano Pochini wrote:
> On 03-Jun-2003 Con Kolivas wrote:
> > I've attempted to answer the question does 1000Hz hurt responsiveness in
> > 2.5 as much as I've found in 2.4; since subjectively the difference
> > wasn't there in 2.5. Using the same config with preempt enabled here are
> > results from 2.5.70-mm3 set at default 1000Hz and at 100Hz (mm31):
>
> Is there any problem using a frequency other than 100 and 1000Hz ?

Not at all. These were chosen because they were the default 2.4 (100) and 2.5 
(1000) frequencies. The large difference in Hz was postulated to increase the 
in-kernel overhead and the amount of time spent tearing down and building up 
the cpu cache again. 2.4 running at 1000Hz shows poor performance at high 
(>4) loads whereas 2.5 doesn't seem to do this. I originally thought it was 
cache thrashing/trashing responsible. However since 2.5 performance is almost 
comparable at 100/1000 it seems to be that the pure interrupt overhead in 2.5 
is lower?

Con

  reply	other threads:[~2003-06-03 10:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-03  3:21 [BENCHMARK] 100Hz v 1000Hz with contest Con Kolivas
2003-06-03  3:36 ` Zwane Mwaikambo
2003-06-03  4:44 ` Nick Piggin
2003-06-03  8:00 ` Giuliano Pochini
2003-06-03 10:36   ` Con Kolivas [this message]
2003-06-03 13:09     ` William Lee Irwin III

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=200306032036.49790.kernel@kolivas.org \
    --to=kernel@kolivas.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pochini@shiny.it \
    /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