linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Giuliano Pochini <pochini@shiny.it>
To: Iain Sandoe <iain@sandoe.co.uk>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: Sound skips
Date: Mon, 26 Mar 2001 12:34:59 +0200 (CEST)	[thread overview]
Message-ID: <XFMail.010326123459.pochini@shiny.it> (raw)
In-Reply-To: <20010326085607.B61492EFD1@apollo.valhalla.net>


>> Ok, I'll try, but this problem regards interrupt latency,
>> not user-spacelatency.
>
> can you be sure it is IRQ and not scheduling latency?

No, but it's likely to be. The audio buffer is 32 fragments (2KB),
that is 1.48s. I don't think an app can remain blocked so long and it
doesn't explain why libtool blocks the sound since it executes in much
less time than one second.

> If so, can you
> identify what driver or function is holding off IRQs for this length of
> time? [a few hundred ms is a 'monstrous' time to hold IRQs off].

Console scrolling does it IFAIK, but this is not the case.

> Andrew's ll patch addresses scheduling latency - i.e. processes
> blocked from running by other processes executing lengthy jobs in system
> state.  For example, fs work done by the kernel on behalf of user processes.

I'll try it.

>> I was fiddling compiling things and I noticed that one of the
>> worst offenders is libtool, a script in the root the the xmms source tree.
>> Just
>> run it to get a 100ms pause. This night I'll check if rt_sigprocmask() keeps
>> irq disabled.
>
> When I last checked it, disk activity was likely to give up to 300 ms
> blocks.  So, the particular culprit (in terms of applications) might be a
> bit misleading - it possibly depends more on how often the buffer cache
> is hit/missed.

This is not the case: libtool doesn't hit the disk.

> Also, if you are IDE-based, make sure that you've used hdparm to allow
> interrupts on during PIO - this makes a huge difference (especially with
> CDROMs).

Nope. All SCSI.

>>Another thing is console scrolling.
>
> yes, console *is/was* bad. - but I read a message going past on Linux Audio
> Dev between Cort & AM that suggested this particular problem had been
> resolved...
>
>  http://www.uow.edu.au/~andrewm/linux/console.html
>
> I'm not fully up-to-date with the state of the LL patches... I'd be
> interested to hear any results you get.

Ok.

Bye.
    Giuliano Pochini ->)|(<- Shiny Network {AS6665} ->)|(<-


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2001-03-26 10:34 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-26  8:56 Sound skips Iain Sandoe
2001-03-26 10:34 ` Giuliano Pochini [this message]
2001-03-28 20:33 ` Giuliano Pochini
  -- strict thread matches above, loose matches on Subject: below --
2001-04-09  9:34 Iain Sandoe
2001-04-08 14:52 Iain Sandoe
2001-04-09  7:56 ` Giuliano Pochini
2001-03-29  8:52 Iain Sandoe
2001-03-29 15:39 ` Giuliano Pochini
2001-04-07 20:39 ` Giuliano Pochini
2001-03-26 11:51 Iain Sandoe
2001-03-26 16:23 ` Geert Uytterhoeven
2001-03-26  4:30 Iain Sandoe
2001-03-26  7:17 ` Giuliano Pochini
2001-03-24 19:45 Iain Sandoe
2001-03-25 19:41 ` Giuliano Pochini
2001-03-24 15:39 Giuliano Pochini

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=XFMail.010326123459.pochini@shiny.it \
    --to=pochini@shiny.it \
    --cc=iain@sandoe.co.uk \
    --cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).