mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Felipe Alfaro Solana <felipe_alfaro@linuxmail.org>
To: in7y118@public.uni-hamburg.de
Cc: LKML <linux-kernel@vger.kernel.org>,
	rhythmbox-devel@gnome.org, gstreamer-devel@lists.sourceforge.net
Subject: Re: Linux 2.6 doesn't like Rhythmbox
Date: Tue, 12 Aug 2003 18:05:54 +0200	[thread overview]
Message-ID: <1060704354.856.1.camel@teapot.felipe-alfaro.com> (raw)
In-Reply-To: <1060699703.3f38fe37b8a1f@rzaixsrv6.rrz.uni-hamburg.de>

On Tue, 2003-08-12 at 16:48, in7y118@public.uni-hamburg.de wrote:

> Let me explain how threads in Rhythmbox work: The main thread is used for the 
> GUI, other threads (mostly idle) take care of the library - reading out 
> artist/title/... tags and monitoring file changes so the playlists gets updated 
> automagically - and then there is a playback thread. This thread is spawned 
> when playback of a file starts (a new one for each file). It starts by 
> inspecting the file and constructing a pipeline depending on the file type (ogg 
> decoder vs mp3 decoder vs ...). This takes half a second, maybe less. After 
> that it proceeds to do read - decode - output to soundcard looping until the 
> song is done playing.
> The priority according to top starts becoming worse from the beginning of 
> playback and gets worse during playback.
> 
> 
> My question now is simple: Who shall I blame for this?

Don't blame anyone still... There's still ongoing kernel scheduler work.
Please, try the latest -mm patches on top of 2.6.0-test3. You will find
them at ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches.

Experiment with 2.6.0-test3-mm1 to see if it still shows the behaviour
you described.


  reply	other threads:[~2003-08-12 16:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-12 14:48 in7y118
2003-08-12 16:05 ` Felipe Alfaro Solana [this message]
2003-08-12 20:07   ` [Rhythmbox-devel] " Colin Walters
2003-08-13 14:59   ` in7y118

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=1060704354.856.1.camel@teapot.felipe-alfaro.com \
    --to=felipe_alfaro@linuxmail.org \
    --cc=gstreamer-devel@lists.sourceforge.net \
    --cc=in7y118@public.uni-hamburg.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rhythmbox-devel@gnome.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

all inboxes | Powered by JetHome®