From: "Iain Sandoe" <iain@sandoe.co.uk>
To: linuxppc-dev@lists.linuxppc.org
Subject: correct use of lock_kernel() - help! please
Date: Mon, 29 Jan 2001 10:29:56 +0000 [thread overview]
Message-ID: <20010129102946.9388A2EFC9@apollo.valhalla.net> (raw)
Hi,
In the driver I am working on (dmasound) someone has placed lock/unlock
_kernel() pairs around whole functions.
This means that (e.g.) if we release the sound device with a lot of
un-played samples at a low-ish sample rate...
AFACIT we could hold the kernel locked for *several seconds*
What do I really need to protect with lock/unlock pairs?
or am I missing something (it wouldn't be the first time ..) ;-?
ciao,
Iain.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2001-01-29 10:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-29 10:29 Iain Sandoe [this message]
2001-01-29 11:05 ` correct use of lock_kernel() - help! please Roman Zippel
-- strict thread matches above, loose matches on Subject: below --
2001-01-29 11:24 Iain Sandoe
2001-01-29 13:39 ` Roman Zippel
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=20010129102946.9388A2EFC9@apollo.valhalla.net \
--to=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).