public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "szonyi calin" <caszonyi@yahoo.com>
To: Billy Biggs <vektor@dumbterm.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: tvtime and the Linux 2.6 scheduler
Date: Mon, 24 May 2004 00:49:08 +0200 (CEST)	[thread overview]
Message-ID: <20040523224908.25194.qmail@web40607.mail.yahoo.com> (raw)
In-Reply-To: <20040523154859.GC22399@dumbterm.net>

 --- Billy Biggs <vektor@dumbterm.net> a écrit : >   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
>   - NTSC, input ~30 fps, each field processed for an output of
> ~60 fps
>   - CPU intensive processing, say 9 ms per field on my P3-733
>   - with a typical AGP card, the X driver takes 4 ms to draw
>   - Wait using /dev/rtc set to 1024 Hz
> 
>   for(;;)
>       9 ms : process frame
>       4 ms : draw frame
>       3 ms : wait until next field time using /dev/rtc
>       9 ms : process frame
>       4 ms : draw frame
>       3 ms : block on /dev/video0 for next frame
>      -----
>      33 ms : time per NTSC frame
> 
>   The theory is that Linux classifies this as a CPU hog
> regardless of
> its priority, and preempts tvtime with other processes. 
> Oswald
> Buddenhagen describes the effect as this:
> 
>   "[...] it starts up fine, but after a few seconds (when the
> scheduler
> gathered some stats) ... well, it looks funny: the scene goes
> roughly
> exponentially into slow motion, then there is a frame drop and
> the
> process starts over.  this behaviour can be observed at any
> priority,
> which is clearly against the claim "no normally priorized
> interactive
> process will preempt a highly priorized cpu-hog" that i've
> read
> somewhere.  the xserver priority does not change anything,
> either;"
> 
>   Avoiding root/SCHED_FIFO and using usleep() instead of
> /dev/rtc seems
> to exhibit the same behavior.
> 
>   Thoughts?
> 

For me it works ok
Running tvtime with 2.6.6-mm5 load average 26 (twenty six) it
works 
almost perfect (no frame skipped -- at least not reported by
tvtime)
at full rate (50 frames/sec). Computer: AMD Duron 700 MHz, 256MB
Ram,
VIA KT133 chipset, AGP 4x, Ati Radeon 7200 

Maybe your users are renicing tvtime ?
AFAIK it is not recommended to renice a process which uses X
server and 
wants realtime processing 

Ohhhhhhhhhh
Take a look at this. Is tvtime's fault (X server does'n have the
chance to display what tvtime processed because tvtime gets
almost all the cpu)

sony@grinch -01:40:31- 0 jobs, ver 2.05b.0 3 
 /~ $ tvtime -s -v
Running tvtime 0.9.12.
Reading configuration from /usr/local/etc/tvtime/tvtime.xml
Reading configuration from /home/sony/.tvtime/tvtime.xml
cpuinfo: CPU AMD Duron(tm) Processor, family 6, model 3,
stepping 1.
cpuinfo: CPU measured at 700,579MHz.
tvtime: Cannot set priority to -19: Permission denied.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

xcommon: Display :0.0, vendor The XFree86 Project, Inc, XFree86
4.4.0
xfullscreen: Single-head detected, pixel aspect will be
calculated.
xfullscreen: Pixel aspect ratio on the primary head is: 75/76 ==
0,99.
xfullscreen: Using the XFree86-VidModeExtension to calculate
fullscreen size.
xfullscreen: Fullscreen to 0,0 with size 1024x768.
xcommon: Have XTest, will use it to ping the screensaver.
xcommon: Pixel aspect ratio 75:76.
xcommon: No window properties found for EWMH.
xcommon: Window manager is not EWMH compliant.
xcommon: Pixel aspect ratio 75:76.
xcommon: Displaying in a 778x576 window inside 778x576 space.
xvoutput: Using XVIDEO adaptor 69: ATI Radeon Video Overlay.
speedycode: Using MMXEXT optimized functions.
station: Reading stationlist from
/home/sony/.tvtime/stationlist.xml
videoinput: Using video4linux2 driver 'bttv', card 'BT878 video
(AVerMedia TVCaptur' (bus PCI:0000:00:09.0).
videoinput: Version is 2318, capabilities 5010015.
tvtime: Sampling input at 720 pixels per scanline.
xcommon: Pixel aspect ratio 75:76.
xcommon: Displaying in a 778x576 window inside 778x576 space.
xcommon: Received a map, marking window as visible (50)

I hope the line above answers your question

>   -Billy
> 
Calin

P.S. Load average is that high because i run freenet
 http://freenet.sourceforge.net -- lots of java processes

=====
--
A mouse is a device used to point at 
the xterm you want to type in.
Kim Alm on a.s.r.


	

	
		
Yahoo! Mail : votre e-mail personnel et gratuit qui vous suit partout ! 
Créez votre Yahoo! Mail sur http://fr.benefits.yahoo.com/

Dialoguez en direct avec vos amis grâce à Yahoo! Messenger !Téléchargez Yahoo! Messenger sur http://fr.messenger.yahoo.com

  parent reply	other threads:[~2004-05-23 22:49 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
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 [this message]
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=20040523224908.25194.qmail@web40607.mail.yahoo.com \
    --to=caszonyi@yahoo.com \
    --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