From: "Jörn Nettingsmeier" <nettings@folkwang.uni-essen.de>
To: Benno Senoner <sbenno@gardena.net>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Roger Larsson <roger.larsson@norran.net>,
"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: Mon, 10 Jul 2000 23:30:40 +0200 [thread overview]
Message-ID: <396A4080.136995CF@folkwang.uni-essen.de> (raw)
In-Reply-To: <00070920393600.02245@smp>
Benno Senoner wrote:
> 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.
i think it's a bad approach to add some warning kludge to modprobe.
keep these tools lean and mean - besides, we wouldn't stand a chance
fiddling with modutils on lkml :)
it's no big deal telling the users to have all modules loaded on
startup and no autoclean.
low-latency users will be willing to take this small effort, and
audio boxen tend to have lots of memory, so dynamic unloading will
not be necessary.
just my....
jorn
--
Jorn Nettingsmeier
Kurfurstenstr. 49
45138 Essen, Germany
http://www.folkwang.uni-essen.de/~nettings/
--
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/
prev parent reply other threads:[~2000-07-10 21:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-07 1:49 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 ` [linux-audio-dev] " Benno Senoner
2000-07-10 21:30 ` Jörn Nettingsmeier [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=396A4080.136995CF@folkwang.uni-essen.de \
--to=nettings@folkwang.uni-essen.de \
--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 \
--cc=sbenno@gardena.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