The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Kasper Sandberg <lkml@metanurb.dk>
To: Andrew Morton <akpm@osdl.org>
Cc: Paul Davis <paul@linuxaudiosystems.com>,
	albert@users.sourceforge.net,
	LKML Mailinglist <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 13:09:49 +0200	[thread overview]
Message-ID: <1089716989.10973.5.camel@localhost> (raw)
In-Reply-To: <20040712172458.2659db52.akpm@osdl.org>

On Mon, 2004-07-12 at 17:24 -0700, Andrew Morton wrote:
> Paul Davis <paul@linuxaudiosystems.com> wrote:
> >
> > >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.
> 
> No, this is wrong.  2.6+preempt can satisfy your latency requirements
> without any scheduling points.  All it requires is that the long-held locks
> be addressed.  I've already done a metric ton of work in that area (notably
> removal of the buffer_head LRUs and rewriting the truncate code) but more
> apparently remains to be done.  We know that reiserfs has problems.
> 
> But what can I do?  I set up a preempt-on-ext3 test box, thrash the crap
> out of it and see 300 usecs worst-case latency.  So I am left empty-handed,
> wondering what on earth is happening out there.
> 
> I am deeply skeptical about claims that autoregulated swappiness can make
> any difference.
> 
> 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.
sorry to interrupt, and i dont know if i get this right, but i have been
using nick piggins patch for quite some time, and it really does
magic :)
> 
> I am also fairly skeptical about claims that voluntary-preempt helps,
> because it only pops a couple of locks, and I doubt that testers are
> hitting the code paths which those changes address anyway.
> 
> So Something Is Up, and I don't know what it is.
> 
> Please double-check that there are no priority inversion problems and that
> the application is correctly setting the scheduling policy and that it is
> mlocking everything appropriately.
> 
> And please ensure that people are setting xrun_debug, and are sending
> reports.
> 
> > 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.
> > 
> 
> Nope, the conditional rescheduling points provide zero benefit on a
> preemptible kernel.
> 
> Something weird is happening, I don't know what it is, I cannot reproduce
> it and I need help understanding what it is, OK?  The sooner we can do
> that, the sooner it gets fixed up.
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 


  parent reply	other threads:[~2004-07-13 11:10 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
2004-07-13 11:09     ` Kasper Sandberg [this message]
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=1089716989.10973.5.camel@localhost \
    --to=lkml@metanurb.dk \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox