public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Con Kolivas <kernel@kolivas.org>
To: Billy Biggs <vektor@dumbterm.net>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: tvtime and the Linux 2.6 scheduler
Date: Mon, 24 May 2004 02:54:19 +1000	[thread overview]
Message-ID: <200405240254.20171.kernel@kolivas.org> (raw)
In-Reply-To: <20040523154859.GC22399@dumbterm.net>

Hi

On Mon, 24 May 2004 01:48 am, Billy Biggs wrote:
>   I am the author of tvtime, a TV application with advanced image
> processing algorithms.  Some users are complaining about poor
> performance under Linux 2.6, and I would like more information about how
> tvtime will be treated by the scheduler.  Here is an example of the
> intended usage:
>
>   - Program running as root and SCHED_FIFO

snip

>      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. 

A program running as sched_fifo it will preempt absolutely everything 
regardless of how it behaves. It sounds like it's giving X less cpu time to 
draw the frame each time until eventually the processing fails to capture the 
frame and then X smooths out again. I cant pretend to understand how your 
application blocks (as you say) between X and tvtime, but does tvtime not try 
to schedule until X has finished using up cpu or will it just run off the 
timer and preempt X away? You say changing priorities doesnt help, but I cant 
tell if you tried this: run the processing sched_normal at lower priority 
than X.

Con

  parent reply	other threads:[~2004-05-23 16:54 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 [this message]
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
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=200405240254.20171.kernel@kolivas.org \
    --to=kernel@kolivas.org \
    --cc=linux-kernel@vger.kernel.org \
    --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