From: Takashi Iwai <tiwai@suse.de>
To: Andrew Morton <akpm@osdl.org>
Cc: Paul Davis <paul@linuxaudiosystems.com>,
albert@users.sourceforge.net, linux-kernel@vger.kernel.org,
florin@sgi.com, linux-audio-dev@music.columbia.edu
Subject: Re: desktop and multimedia as an afterthought?
Date: Tue, 13 Jul 2004 10:30:13 +0200 [thread overview]
Message-ID: <s5hfz7wb97u.wl@alsa2.suse.de> (raw)
In-Reply-To: <20040712172458.2659db52.akpm@osdl.org>
At Mon, 12 Jul 2004 17:24:58 -0700,
Andrew Morton wrote:
>
> I am deeply skeptical about claims that CPU scheduler changes make any
> difference. A scheduler change shouldn't improve responsiveness of
> !SCHED_OTHER tasks at all, so perhaps there are application priority
> inversion problems, or applications aren't setting SCHED_FIFO/RR correctly.
> I do not know.
Regarding the JACK problem, it seems that the incompatibility with
NPTL (SCHED_INHERIT is default) did wrong.
Taking a look through the thread, I feel that very different topics
are argued in the single "desktop" problem, namely, the interactivity
and the latency. The latter, the problem of real-time audio
(e.g. JACK), must be irrelevant with the CPU scheduler. It can
be fixed by detecting the too long critical sections, but the fix
won't always improve the interactivity.
OTOH, the interactivity can be, and should be improved somehow with
tuning of CPU scheduler. However, even about this word, we discuss
totally different meanings. For example, the GUI response and the
fluent audio/video playback. The improvement of the former doesn't
imply the improvement of the latter (often contradictorily)...
--
Takashi Iwai <tiwai@suse.de> ALSA Developer - www.alsa-project.org
next prev parent reply other threads:[~2004-07-13 8:30 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
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 [this message]
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=s5hfz7wb97u.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=akpm@osdl.org \
--cc=albert@users.sourceforge.net \
--cc=florin@sgi.com \
--cc=linux-audio-dev@music.columbia.edu \
--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.