linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Clark Williams <williams@redhat.com>
To: jordan <triplesquarednine@gmail.com>
Cc: Daniel James <daniel@64studio.com>,
	John Kacur <jkacur@redhat.com>,
	Gautam Thaker <gautam.h.thaker@lmco.com>,
	linux-rt-users@vger.kernel.org
Subject: Re: "yum install ...." based instruction on building a RT kernel.
Date: Sun, 19 Sep 2010 10:49:16 -0500	[thread overview]
Message-ID: <20100919104916.63967cc4@riff> (raw)
In-Reply-To: <AANLkTint6iHc6DPeEVpKd0ER0XsYMDK=0yiekHGkWtWF@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2034 bytes --]

On Sat, 18 Sep 2010 15:24:18 -0400
jordan <triplesquarednine@gmail.com> wrote:

> > Being a release or two behind the bleeding edge is no bad thing for that
> > type of user either - if (for instance) 2.6.31-rt works fine in a
> > production audio system, there's no big hurry to change it and
> > potentially break stuff. For that sort of user, high availability is
> > much more important than squeezing every last drop of performance out of
> > the hardware.
> 
> true enough. 2.6.32 and 2.6.33 are much nicer though...

I'll second this sentiment. We were going to to release a new realtime
kernel with the .31 series, but testing showed that it had some
significant regressions in terms of event response time and in overall
throughput, so we held off. The .33 series is much better in those
regards and that's what we'll be going out with in our next release. 

> 
> > In audio recording, we're potentially capturing once-in-a-lifetime or
> > one-time-ever events, particularly since the industry focus has shifted
> > from the studio to the live stage - whether TV, stadium or festival,
> > that's where the artists are making their living these days. Even
> > festivals run to tight schedules, with only 15 minutes allowed to switch
> > between acts, including moving all the gear and repatching it. You can't
> > ask the band to go and get a beer while you recompile your kernel :-)
> 
> Ideally, no one would ever be compiling the kernel at a show, lol. I
> know I never would! lol....that's hilarious.
> You do that stuff on your own time!  Artists have always made their
> money live, and through merchandise. Record sales go into the Label's
> pockets for the most part.
> 

Heh. I haven't actually compiled a kernel on stage, but a friend of
mine reworked a play's audio track 20 minutes before curtain when the
Windows box ate it's disk; he booted up his Linux laptop and ran the
sound sequencer program in a QEMU instance. I think I'd rather rebuild
a kernel under the gun :).


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2010-09-19 15:49 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-16 22:54 "yum install ...." based instruction on building a RT kernel Gautam Thaker
2010-09-17  6:08 ` jordan
2010-09-17  7:08   ` John Kacur
2010-09-17 12:38     ` Daniel James
2010-09-17 13:06       ` Bernardo Barros
2010-09-17 15:25         ` EXTERNAL: " Gautam Thaker
2010-09-18 19:34           ` jordan
2010-09-17 13:10       ` John Kacur
2010-09-18 19:24       ` jordan
2010-09-19 15:49         ` Clark Williams [this message]
2010-09-19 17:23           ` jordan
2010-09-19 19:20             ` Bernardo Barros
2010-09-19 20:00               ` jordan
2010-10-17 15:20               ` jordan
2010-10-18  6:16                 ` John Kacur
2010-10-18  7:12                   ` jordan
2010-09-18 19:15     ` jordan
2010-09-18 20:06       ` jordan

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=20100919104916.63967cc4@riff \
    --to=williams@redhat.com \
    --cc=daniel@64studio.com \
    --cc=gautam.h.thaker@lmco.com \
    --cc=jkacur@redhat.com \
    --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).