From: David Sommerseth <dazo@users.sourceforge.net>
To: jordan johnston <triplesquarednine@gmail.com>
Cc: linux-rt-users@vger.kernel.org
Subject: Re: advanced tips for reducing latency?
Date: Wed, 04 Aug 2010 13:16:37 +0200 [thread overview]
Message-ID: <4C594C15.7070900@users.sourceforge.net> (raw)
In-Reply-To: <AANLkTikqLyNuPgjDhLfVjrhUWzCxocPkM=dh6yAJKq7Z@mail.gmail.com>
On 04/08/10 13:03, jordan johnston wrote:
> hello,
>
> I am new to the list, but not new to using linux for pro-audio and
> thus the rt-patches...
> I'm looking for possibly some advanced tweaks to further reduce
> latency on my system.
> things i am already aware of;
[...snip...]
Hi Jordan,
You might find some useful hints in these docs:
<http://www.redhat.com/docs/en-US/Red_Hat_Enterprise_MRG/1.2/html/Realtime_Tuning_Guide/index.html>
<http://www.redhat.com/docs/en-US/Red_Hat_Enterprise_MRG/1.2/html/Realtime_Reference_Guide/index.html>
kind regards,
David Sommerseth
prev parent reply other threads:[~2010-08-04 11:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-04 11:03 advanced tips for reducing latency? jordan johnston
2010-08-04 11:16 ` David Sommerseth [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=4C594C15.7070900@users.sourceforge.net \
--to=dazo@users.sourceforge.net \
--cc=linux-rt-users@vger.kernel.org \
--cc=triplesquarednine@gmail.com \
/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).