public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jose Luis Domingo Lopez <linux-kernel@24x7linux.com>
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: Sun, 23 May 2004 18:20:08 +0200	[thread overview]
Message-ID: <20040523162008.GA14482@localhost> (raw)
In-Reply-To: <20040523154859.GC22399@dumbterm.net>

On Sunday, 23 May 2004, at 10:48:59 -0500,
Billy Biggs wrote:

>   "[...] 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;"
> 
I am currently using tvtime 0.9.12-2 from Debian SID on a Linux kernel
version 2.6.6 compiled with Sid's gcc 3.3.3 and haven't seen such
problems so far. I use tvtime often to watch TV on my monitor, and it
works OK, no artifacts and no slowdown (even when I download my email
and spamassassin starts to eat CPU cicles like mad).

With my current configuration tvtime at full screen (1024x768) takes
about 40% CPU from a AMD XP 1477 MHz (1700 rating). I have just tried
launching three copies of "yes" on several aterm's and tvtime still
looks as smooth as before, althoug CPU is always at 100%

Please ask for more information should you need it.

-- 
Jose Luis Domingo Lopez
Linux Registered User #189436     Debian Linux Sid (Linux 2.6.6)

  reply	other threads:[~2004-05-23 16:20 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 [this message]
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
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=20040523162008.GA14482@localhost \
    --to=linux-kernel@24x7linux.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