From: est@hyperreal.org
To: linux-sound@vger.kernel.org
Subject: latency killers..devourers of cpus
Date: Thu, 27 May 1999 14:21:33 +0000 [thread overview]
Message-ID: <marc-linux-sound-92799469503865@msgid-missing> (raw)
Greetings!
I was wondering what the collective wisdom was about what things in
linux can monopolize the cpu for unpleasant periods of time.
Obviously such things are unpleasant for responsive sound software.
I'm particularly interested in things which can preempt even POSIX
`real-time' processes. These would probably be things happening in
the kernel that aren't owned by any particular process.
Two examples that I've confirmed are:
* IDE drives..just forget it.
* Access to the /proc file-system, such as is done by ps(1) and
top(1)..this is definitely a back-door to denial-of-cpu.
Also, does anyone know of good places to post this query?
Many thanks in advance! :)
E
reply other threads:[~1999-05-27 14:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=marc-linux-sound-92799469503865@msgid-missing \
--to=est@hyperreal.org \
--cc=linux-sound@vger.kernel.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