All of lore.kernel.org
 help / color / mirror / Atom feed
From: Con Kolivas <kernel@kolivas.org>
To: Paul Davis <paul@linuxaudiosystems.com>
Cc: Albert Cahalan <albert@users.sourceforge.net>,
	linux-kernel mailing list <linux-kernel@vger.kernel.org>,
	florin@sgi.com
Subject: Re: desktop and multimedia as an afterthought?
Date: Tue, 13 Jul 2004 10:18:08 +1000	[thread overview]
Message-ID: <cone.1089677888.268686.12958.502@pc.kolivas.org> (raw)
In-Reply-To: 200407122354.i6CNsNqS003382@localhost.localdomain

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

Paul Davis writes:

>>It's too bad that the multimedia community didn't participate
>>much during the 2.5.xx development leading up to 2.6.0. If they
>>had done so, the situation might be different today. Fortunately,
>>fixing up the multimedia problems isn't too risky to do during
>>the stable 2.6.xx series.
> 
> I regret that this description is persisting here. "We" (the audio
> developer community) did not participate because it was made clear
> that our needs were not going to be considered. We were told that the
> preemption patch was sufficient to provide "low latency", and that
> rescheduling points dotted all over the place was bad engineering
> (probably true). With this as the pre-rendered verdict, there's not a
> lot of point in dedicating time to tracking a situation that clearly
> is not going to work.
> 
> The kernel is not going to provide adequate latency for multimedia
> needs without either (1) latency issues being front and center in
> every kernel developer's mind, which seems unlikely and/or (2)
> conditional rescheduling points added to the kernel, which appears to
> require non-mainstreamed patches.

Please dont start a low level flamewar over this. Latency is firmly on the 
agenda and under consideration for the mainline kernel now. 

There is nothing wrong with using a dedicated alternative patchset for 
specific tasks, as long as any lessons learnt from it are also taken into 
consideration for mainline. Mainline kernels must have (high gain)/(low 
risk) ratio changes only. 

Rather than just saying that the desktop and multimedia is not considered it 
would be more helpful to say what helps where and why in the public forum of 
the main kernel mailing list. Off list discussion can go completely 
unnoticed (even I wasn't aware of my patchset being used and quoted!)

Cheers,
Con


[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2004-07-13  0:19 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-12 20:45 desktop and multimedia as an afterthought? Albert Cahalan
2004-07-12 23:54 ` Paul Davis
2004-07-13  0:18   ` Con Kolivas [this message]
2004-07-13  1:11     ` Paul Davis
2004-07-13  3:25     ` Florin Andrei
2004-07-13  0:24   ` Andrew Morton
2004-07-13  1:49     ` Thomas Charbonnel
2004-07-13 10:22       ` Andrew Morton
2004-07-13 11:01         ` Thomas Charbonnel
2004-07-13  3:22     ` Florin Andrei
2004-07-13  8:30     ` Takashi Iwai
2004-07-13 11:09     ` Kasper Sandberg
2004-07-13 12:09     ` [linux-audio-dev] " Martijn Sipkema
2004-07-13 14:55       ` Paul Davis
2004-07-13 22:37         ` Martijn Sipkema
2004-07-13 22:31           ` Fons Adriaensen
2004-07-13 19:12       ` Bill Huey
2004-07-13 20:00         ` Lee Revell
2004-07-13 22:44         ` Martijn Sipkema
2004-07-13 22:08           ` Bill Huey
2004-07-13 23:37             ` Martijn Sipkema
  -- strict thread matches above, loose matches on Subject: below --
2004-07-12 18:57 Florin Andrei
2004-07-12 19:12 ` Mark Hahn
2004-07-12 20:47   ` Paul Davis
2004-07-12 21:25   ` Florin Andrei

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=cone.1089677888.268686.12958.502@pc.kolivas.org \
    --to=kernel@kolivas.org \
    --cc=albert@users.sourceforge.net \
    --cc=florin@sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paul@linuxaudiosystems.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 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.