From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Kon Colivas is working again on a new scheduler for Desktop/Multimedia/Gaming PCs
Date: Sat, 5 Sep 2009 11:39:18 +0200 [thread overview]
Message-ID: <200909051139.18578.alan.mckinnon@gmail.com> (raw)
In-Reply-To: <200909050206.05935.volkerarmin@googlemail.com>
On Saturday 05 September 2009 02:06:05 Volker Armin Hemmann wrote:
> > Fire up Ardour and record 32 channels of audio at the same time set to
> > <5mS latency using Jack and see if whatever version of the mainline
> > kernel you are running doesn't have. I've recorded as many as 48
> > channels @ 48KHz across three hard drives at less than 2mS on my main
> > recording platform, but that requires rt-sources. I doubt I could do
> > better than about 25mS with vanilla-sources.
> >
> > Just my experience,
> > Mark
>
> well, and your workload asks for rt. But rt also means overhead, reduction
> of performance. So why cater for 1 in a thousand system and punish the
> other 999?
>
> if you like the 'bfs' scheduler, that is great.
>
I think it's more a case of a whole lot less than 1 in a thousand, and your
workload intersects with it in no way at all.
There's a huge need for a low latency rt kernel and a massive market for it.
But it's not mainline and shouldn't even be in there. It should be something
separate and parallel. If Kon's new patches are good, I hope it gains traction
- his previous stuff was very good. This is the beauty of open source Linux,
we can do stuff like this trivially easy.
Imagine a distro or an ebuild built just for audio and gaming work that's
easypeasy to install and use. We can do that in about a fortnight.
--
alan dot mckinnon at gmail dot com
next prev parent reply other threads:[~2009-09-05 9:40 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-04 23:36 [gentoo-user] Kon Colivas is working again on a new scheduler for Desktop/Multimedia/Gaming PCs Nikos Chantziaras
2009-09-04 23:43 ` Volker Armin Hemmann
2009-09-04 23:50 ` Mark Knecht
2009-09-05 0:06 ` Volker Armin Hemmann
2009-09-05 0:18 ` [gentoo-user] " Nikos Chantziaras
2009-09-05 14:11 ` Frank Steinmetzger
2009-09-05 14:17 ` Volker Armin Hemmann
2009-09-05 14:51 ` Frank Steinmetzger
2009-09-05 14:59 ` Volker Armin Hemmann
2009-09-05 19:58 ` Nikos Chantziaras
2009-09-05 22:48 ` Volker Armin Hemmann
2009-09-05 23:06 ` Alan McKinnon
2009-09-05 23:23 ` Volker Armin Hemmann
2009-09-06 0:32 ` Nikos Chantziaras
2009-09-06 0:43 ` Volker Armin Hemmann
2009-09-06 0:52 ` Nikos Chantziaras
2009-09-06 2:08 ` Volker Armin Hemmann
2009-09-06 2:15 ` Nikos Chantziaras
2009-09-06 11:26 ` Volker Armin Hemmann
2009-09-07 19:58 ` Volker Armin Hemmann
2009-09-07 20:38 ` Alan McKinnon
2009-09-05 23:08 ` Nikos Chantziaras
2009-09-05 23:26 ` Volker Armin Hemmann
2009-09-06 0:34 ` Nikos Chantziaras
2009-09-06 0:44 ` Volker Armin Hemmann
2009-09-06 0:48 ` Nikos Chantziaras
2009-09-06 0:56 ` Volker Armin Hemmann
2009-09-06 0:50 ` Volker Armin Hemmann
2009-09-06 0:53 ` Nikos Chantziaras
2009-09-06 1:08 ` Nikos Chantziaras
2009-09-06 2:10 ` Volker Armin Hemmann
2009-09-06 2:21 ` Nikos Chantziaras
2009-09-06 2:56 ` Nikos Chantziaras
2009-09-06 11:27 ` Volker Armin Hemmann
2009-09-05 9:39 ` Alan McKinnon [this message]
2009-09-04 23:57 ` Nikos Chantziaras
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=200909051139.18578.alan.mckinnon@gmail.com \
--to=alan.mckinnon@gmail.com \
--cc=gentoo-user@lists.gentoo.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