All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ove Karlsen <ove.karlsen@paradoxuncreated.com>
To: Damien Moody <webmaster@gentoostudio.org>
Cc: linux-rt-users@vger.kernel.org
Subject: Re: rt kernel, pro-audio use
Date: Thu, 20 Dec 2012 09:36:51 +0100	[thread overview]
Message-ID: <50D2CE23.2050303@paradoxuncreated.com> (raw)
In-Reply-To: <50D231F5.4060604@gentoostudio.org>

On 12/19/2012 10:30 PM, Damien Moody wrote:
> Hi,
>
> I have a couple of questions.
>
> 1. I'd like to keep informed when the rt kernel gets updated, so I can 
> put up a new Gentoo ebuild on my site (gentoostudio.org). Is this the 
> list for that? If not, what is?
>
> 2. I use the rt patches a la rt-sources on Gentoo. I'm a musician and 
> audio engineer. What advantages does the rt patch set provide over 
> other patch sets like ck-sources and pf-sources, where latency can be 
> configured to be very low? I'd like to document this on my site.
>
> Thanks!
> Damien
> -- 
> To unsubscribe from this list: send the line "unsubscribe 
> linux-rt-users" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
1 - yes. Have your email client filter mails with "announce" in the 
header, to "rt kernel updates" folder for instance. Something like that.

2 - rt-patch provides extremely low latency, if you hardware can handle 
it. Intel E5 is a good cpu, for extreme low latency.
Ck-patches doesn`t really provide any improvement over fair-scheduler. 
Actually fair-scheduler performs on overall better, with lower peak 
latencies. Ck-patches has slightly lower average latencies. While 
audio-performance was similar when I tested both, visual jitter, was 
less with fair scheduler, and 90hz timer.

I did some tests to make linux run with the least-jitter possible. You 
can read the conlusions on that here: 
http://paradoxuncreated.com/Blog/wordpress/?p=2268

It seems RT-patch is not neccesary for very low latency audio, and a 
good firewire card, atleast on the old firewire-stack, hopefully the new 
one is as good at latency, where I ran audio at 0.33ms latency, with 
RT-threads.

The rt-patch using only threadmode, (not impacting performance, other 
than on the thread it is used) might be good for audio, since visual 
jitter already can be minimized on the regular kernel. if 0.33 should 
not work with standard and it is a software problem, or you want to try 
even lower. 0.2ms is very close to virtual hardware, and ofcourse is 
something a musician would want.

Other than that RT patch might have specific uses outside general 
computing and media.

Peace Be With You.





  reply	other threads:[~2012-12-20  8:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-19 21:30 rt kernel, pro-audio use Damien Moody
2012-12-20  8:36 ` Ove Karlsen [this message]
2012-12-20 17:00 ` Clark Williams

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=50D2CE23.2050303@paradoxuncreated.com \
    --to=ove.karlsen@paradoxuncreated.com \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=webmaster@gentoostudio.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.