From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Ingo Molnar <mingo@elte.hu>
Cc: Con Kolivas <kernel@kolivas.org>,
Billy Biggs <vektor@dumbterm.net>,
Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: tvtime and the Linux 2.6 scheduler
Date: Mon, 24 May 2004 16:58:29 +1000 [thread overview]
Message-ID: <40B19D15.1090105@yahoo.com.au> (raw)
In-Reply-To: <20040524084334.GB24967@elte.hu>
Ingo Molnar wrote:
> * Con Kolivas <kernel@kolivas.org> wrote:
>
>
>>> 33 ms : time per NTSC frame
>>
>>snip
>>
>>The followup email from someone describing good performance may help
>>us understand what's going on. Your example of poor performance is one
>>when the cpu performance is marginal to get exactly 30 fps processed
>>and on the screen. The cpu overhead in 2.6 is slightly higher than 2.4
>>so a borderline case may be just pushed over.
>
>
> most of the cpu overhead comes from HZ=1000. Especial with SCHED_FIFO
> there should be minimal (if any) impact from the scheduler changes -
> SCHED_FIFO tasks get all CPU time, no ifs and whens.
>
> could people who experience tvtime performance problems apply the patch
> below to change HZ back to 100? Does it have any impact?
>
Just one other thing - realtime scheduling was basically broken up
until around 2.6.5. Before starting any tests, please ensure first
that you are using at least the 2.6.5 kernel. Thanks.
next prev parent reply other threads:[~2004-05-24 6:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-23 15:48 tvtime and the Linux 2.6 scheduler Billy Biggs
2004-05-23 16:20 ` Jose Luis Domingo Lopez
2004-05-23 16:54 ` Con Kolivas
2004-05-23 17:20 ` Billy Biggs
2004-05-23 21:03 ` Oswald Buddenhagen
2004-05-24 8:43 ` Ingo Molnar
2004-05-24 6:58 ` Nick Piggin [this message]
2004-05-24 9:12 ` Ingo Molnar
2004-05-24 7:14 ` Nick Piggin
2004-05-24 9:34 ` Ingo Molnar
2004-05-23 22:49 ` szonyi calin
2004-05-24 19:38 ` Bill Davidsen
2004-05-25 8:49 ` Tobias Diedrich
2004-05-24 9:20 ` Ingo Molnar
2004-05-24 11:45 ` Oswald Buddenhagen
2004-05-27 11:35 ` Redeeman
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=40B19D15.1090105@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=kernel@kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=vektor@dumbterm.net \
/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