linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Davide Libenzi <davidel@xmailserver.org>
To: Roger Larsson <roger.larsson@skelleftea.mail.telia.com>
Cc: Takashi Iwai <tiwai@suse.de>, Daniel Phillips <phillips@arcor.de>,
	Steven Newbury <s_j_newbury@yahoo.co.uk>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: SCHED_SOFTRR patch (memory lock?)
Date: Tue, 13 Jan 2004 11:48:58 -0800 (PST)	[thread overview]
Message-ID: <Pine.LNX.4.44.0401131145490.12810-100000@bigblue.dev.mdolabs.com> (raw)
In-Reply-To: <200308072005.07017.roger.larsson@skelleftea.mail.telia.com>

On Thu, 7 Aug 2003, Roger Larsson wrote:

> On Thursday 07 August 2003 18.31, Takashi Iwai wrote:
> > At Thu, 7 Aug 2003 16:59:03 +0100,
> >
> > Daniel Phillips wrote:
> > > > Under 2.6.0-test1 based kernels I have experienced quite a lote of
> > > > drop-outs with XMMS playing mp3's with a moderate load, however, when
> > > > run as root (with SCHED_RR) I encountered no drop-outs at all.  When
> > > > using SOFTRR under I had very choppy playback when the machine was
> > > > under load. It was a constant jittering more than intermittent
> > > > drop-outs.
> > >
> > > According to me, this should not happen, since your cpu usage is well
> > > below what is supposed to be the cutoff for the realtime slice.  I've
> > > only seen one report like yours, where SOFTRR isn't working as intended. 
> > > On the other hand, I've missed a lot of lkml traffice lately, so there
> > > could be more.
> >
> > looking at the source code of xmms and found that xmms OSS output
> > plugin behaves differently if the process is SCHED_RR.
> > when xmms is started with SCHED_RR, it won't create an (another) audio
> > thread.  perhaps this explains also the difference found in some
> > cases.
> >
> > well, i'm not 100% sure about this theory, now needs to practice :)
> > please try to turn off the check of SCHED_RR in
> > xmms/Output/OSS/audio.c, something like:
> >
> >         realtime = xmms_check_realtime_priority();
> >
> > replaced with
> >
> > 	realtime = 0;
> 
> Another possibility - will XMMS lock its memory from swapping when running as 
> root? (Or are there any special allocation/IO rule for root?)

Gee, it was 100F last time I saw this thread :-)
Yes, xmms behave in two completely different ways depending on the fact 
that it is or it is not running RR. With RR it writes directly to the dsp, 
while w/out it creates a thread that handles an output buffer. Then thread 
then does write to the dsp when the buffer has something to be written.




- Davide



      reply	other threads:[~2004-01-13 19:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-28 20:27 SCHED_SOFTRR patch Steven Newbury
2003-08-07 15:59 ` Daniel Phillips
2003-08-07 16:31   ` Takashi Iwai
2003-08-07 18:05     ` SCHED_SOFTRR patch (memory lock?) Roger Larsson
2004-01-13 19:48       ` Davide Libenzi [this message]

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=Pine.LNX.4.44.0401131145490.12810-100000@bigblue.dev.mdolabs.com \
    --to=davidel@xmailserver.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=phillips@arcor.de \
    --cc=roger.larsson@skelleftea.mail.telia.com \
    --cc=s_j_newbury@yahoo.co.uk \
    --cc=tiwai@suse.de \
    /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;
as well as URLs for NNTP newsgroup(s).