From: Benno Senoner <sbenno@gardena.net>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Roger Larsson <roger.larsson@norran.net>
Cc: "linux-kernel@vger.rutgers.edu" <linux-kernel@vger.rutgers.edu>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-audio-dev@ginette.musique.umontreal.ca"
<linux-audio-dev@ginette.musique.umontreal.ca>
Subject: Re: [linux-audio-dev] Re: new latency report
Date: Sun, 9 Jul 2000 20:13:47 +0200 [thread overview]
Message-ID: <00070920393600.02245@smp> (raw)
In-Reply-To: <E13BL8P-00022Z-00@the-village.bc.nu>
On Sun, 09 Jul 2000, Alan Cox wrote:
> > and the 704ms used to busy loop in modprobe...
> > (SB16 non PnP)
>
> I take patches for the sb16 if it bugs you enough to fix it.
The point is that modprobe will be a general problem:
many modules will freeze your box for dozen if not hundreds of msecs.
( eg aic7xxx )
We can live with this if we require that the user insmods all the modules
at boottime.
The problem could be the audiomatic module loading / cleaning
(kmod).
For example how do we know in advance that the user wants to use
pppd ? (ppp.o , slhc.o )
If he is offline while doing low-latency audio , and suddenly needs
something from the net, as soon as he fires up pppd, a latency-peak
may occur.
So a way to avoid latency peaks would be to inform the user, that
if (during his audio recording sessions) he wants to do some stuff which
requires module loading , he has to preload the modules at boottime,
and disable automatic module cleanup.
Anyone better ideas ?
Benno.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux.eu.org/Linux-MM/
next prev parent reply other threads:[~2000-07-09 18:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-07 1:49 new latency report Roger Larsson
2000-07-07 3:21 ` Andrew Morton
2000-07-07 14:38 ` Oliver Xymoron
2000-07-09 17:44 ` Alan Cox
2000-07-09 18:13 ` Benno Senoner [this message]
2000-07-10 21:30 ` [linux-audio-dev] " Jörn Nettingsmeier
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=00070920393600.02245@smp \
--to=sbenno@gardena.net \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-audio-dev@ginette.musique.umontreal.ca \
--cc=linux-kernel@vger.rutgers.edu \
--cc=linux-mm@kvack.org \
--cc=roger.larsson@norran.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.