From: "Iain Sandoe" <iain@sandoe.co.uk>
To: linuxppc-dev@lists.linuxppc.org
Subject: Kernel profiling and sound
Date: Mon, 26 Jun 2000 17:19:56 +0100 [thread overview]
Message-ID: <200006261623.RAA10793@hyperion.valhalla.net> (raw)
Hi List,
One of my main interests is in using linuxppc for DSP/Audio related tasks.
I am on the ALSA & audio-dev lists and there has been a lot of discussion
about achieving low-latency audio I/O.
Could anyone enlighten me as to the state of this topic wrt the linuxppc
kernels? It seems to be almost exclusively x86-related.
Specifically:
How does one profile the kernel?
Is there anyone (else) on the list who is trying to do the same kind of
thing?
Has anyone tried applying the low-latency patches (Ingo's) to *any* ppc
kernel?
does the ppc 2.4 kernel suffer from the (reported) VM issue that causes it
to exhibit *more* latency than 2.2.x kernels (this is the ststus of x86)?
I'm sure I'll have more questions soon...
TIA,
Iain.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
reply other threads:[~2000-06-26 16:19 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=200006261623.RAA10793@hyperion.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).