linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Knecht <markknecht@gmail.com>
To: Pedro Ribeiro <pedrib@gmail.com>
Cc: linux-rt-users@vger.kernel.org
Subject: Re: future of -rt kernels for realtime audio
Date: Tue, 6 Jul 2010 08:45:14 -0700	[thread overview]
Message-ID: <AANLkTinznqiQuo3g30kFuEViJwc3bnd4P3Xoar4TJw6y@mail.gmail.com> (raw)
In-Reply-To: <AANLkTikZNjYJnDM6iKgrT1230FP8DSMgHUrZz2lYL4ll@mail.gmail.com>

On Tue, Jul 6, 2010 at 4:19 AM, Pedro Ribeiro <pedrib@gmail.com> wrote:
> Hi,
>
> I've been using -rt kernels since 2.6.29 because I do realtime audio
> on my laptop.
>
> The audio stability has been steadily improving since, and now I find
> that I can use 2.6.34 without the -rt patch and achieve the same
> stability as 2.6.33-rt - well, my latency requirements aren't that
> high, I just need to maintain 8.9ms completely stable, however before
> .34 it would be impossible without the -rt patch.
>
> So out of curiosity, what changed for .34? According to [1], on .33
> Raw Spinlock Annotation was introduced in the mainline kernel.
> However, as said above, I can't get the same performance than with
> .34.
>
> I remember that I read somewhere that the one the biggest problems
> with latency requirements was the use of the BKL. Do you think there
> will be a significant improvement of latency (in specific cases of
> course) with the scheduled removal of BKL for 2.6.36?
>
> Thanks for the help,
> Pedro
>
> [1] http://www.osadl.org/Realtime-Linux.projects-realtime-linux.0.html

With my HDSP 9652 and a good quality desktop machine I've been able to
achieve <2mS latency for over a couple of years with the standard
kernel, but only under controlled setups. If I'm just doing audio and
I run nothing else, doing my best to ensure the machine won't jump
into some cron job that uses a lot of disk access, etc., then the main
line kernel works fine and has for me for quite a long time.

In my experience the value of rt-sources is that I don't have to be as
careful. I can open a broswer, do a little email, etc., or even build
some code and still not get xruns. I cannot do that today with the
main line kernel.

So, I think it's not that the basic Linux kernel cannot do the job
because it can. I suggest it's more about how much extra protection do
you want or need? If you've got a machine that's fully dedicated to
audio then possibly you could get away with it. If you are using this
machine for additional tasks then being able to control real-time
priorities will like win out every time.

Cheers,
Mark

  parent reply	other threads:[~2010-07-06 15:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-06 11:19 future of -rt kernels for realtime audio Pedro Ribeiro
2010-07-06 11:49 ` Robin Gareus
2010-07-06 15:45 ` Mark Knecht [this message]
2010-07-06 19:53 ` Philipp Überbacher
2010-07-06 20:44   ` Pedro Ribeiro

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=AANLkTinznqiQuo3g30kFuEViJwc3bnd4P3Xoar4TJw6y@mail.gmail.com \
    --to=markknecht@gmail.com \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=pedrib@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).