From: Oswald Buddenhagen <ossi@kde.org>
To: Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: tvtime and the Linux 2.6 scheduler
Date: Sun, 23 May 2004 23:03:13 +0200 [thread overview]
Message-ID: <20040523210313.GA16310@ugly.local> (raw)
In-Reply-To: <200405240254.20171.kernel@kolivas.org>
On Mon, May 24, 2004 at 02:54:19AM +1000, Con Kolivas wrote:
> 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.
>
"his" example is in fact mine. 2.4 ghz chew 25 fps. the total cpu load
is at 30-40% (depending on the selected deinterlacer algorithm).
> A program running as sched_fifo it will preempt absolutely everything
> regardless of how it behaves.
>
errm ... right. i paid too little attention to this "tiny" detail.
*blush*
now i hacked tvtime to simply ignore v4l2 ... and guess what? it works
...
so the new theory is, that tvtime has some problem with v4l2 input
buffering ...
greetings
--
Hi! I'm a .signature virus! Copy me into your ~/.signature, please!
--
Chaos, panic, and disorder - my work here is done.
next prev parent reply other threads:[~2004-05-23 21:03 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 [this message]
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=20040523210313.GA16310@ugly.local \
--to=ossi@kde.org \
--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