From: Andrew Morton <akpm@zip.com.au>
To: Davide Libenzi <davidel@xmailserver.org>
Cc: "Dieter Nützel" <Dieter.Nuetzel@hamburg.de>,
"Robert Love" <rml@tech9.net>,
"Linux Kernel List" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Balanced Multi Queue Scheduler ...
Date: Sat, 29 Dec 2001 14:49:25 -0800 [thread overview]
Message-ID: <3C2E4875.9D0F4BC6@zip.com.au> (raw)
In-Reply-To: <20011229051712Z287139-18284+8656@vger.kernel.org> <Pine.LNX.4.40.0112291424560.1580-100000@blue1.dev.mcafeelabs.com>
Davide Libenzi wrote:
>
> On Sat, 29 Dec 2001, Dieter [iso-8859-15] Nützel wrote:
>
> > Davide worte:
> > > There's a bug fix and the use of the Time Slice Split Scheduler inside the
> > > local CPUs schedulers. Versions from 0.46 to 0.52 are broken by the fixed
> > > bug so testers should use this version :
> > >
> > > http://www.xmailserver.org/linux-patches/mss-2.html#patches
> >
> > Sorry, if someone asks this before but do you think that you get some stuff
> > out of it for 2.4.xx?
> >
> > Your numbers for the 8 SMP system are great.
> > Can't wait to do some tests on my poor single 1 GHz Athlon II and soon dual
> > Athlon MP/XP 1600+ on an MS 6501 (AMD 760MPX).
> >
> > Maybe my MP3/Ogg-Vorbis hiccup during dbench 32+ are solved?
> > Currently running latest 2.4.17+preempt (do think that can be mixed with your
> > new scheduler?).
>
> The new patch need ver >= 2.5.2-pre3 because Linus merged the Time Slice
> Split Scheduler and making it to apply to 2.4.x could be a pain in the b*tt.
> Yes, as i expected numbers on big SMP are very good but still i don't
> think that this can help you with your problem.
I would expect the audio dropouts to be due to disk read latencies
and insufficiently large buffers in the audio app, and/or failure
of that audio app to mlock itself down.
If it's scheduling latency, which I doubt, I yesterday put out
a 2.4.17 low-latency patch which has a worst-case latency which is
two orders of magnitude less that the preemptive kernel's. The
lock-break patch will improve the preempt patch's worst case.
http://www.zip.com.au/~akpm/linux/2.4.17-low-latency.patch.gz
> It'd be nice to have inside local_irq_disable()/enable() a cycle counter
> sampler to see what is the worst case path with disabled irqs.
>
http://www.zip.com.au/~akpm/linux/#intlat
This tool needs a bit of maintenance work, but it can measure and identify
the source of worst-case interrupt latencies quite successfully.
-
next prev parent reply other threads:[~2001-12-29 22:55 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-29 5:16 [PATCH] Balanced Multi Queue Scheduler Dieter Nützel
2001-12-29 22:29 ` Davide Libenzi
2001-12-29 22:49 ` Andrew Morton [this message]
2001-12-29 23:39 ` Davide Libenzi
2001-12-29 23:38 ` Stephan von Krawczynski
2001-12-30 0:02 ` Davide Libenzi
2001-12-30 2:32 ` Alan Cox
2001-12-30 3:11 ` Dieter Nützel
2001-12-30 19:47 ` Timothy Covell
2001-12-30 20:16 ` Davide Libenzi
2001-12-30 23:20 ` Stephan von Krawczynski
2001-12-30 23:46 ` Davide Libenzi
2001-12-31 16:37 ` Stephan von Krawczynski
2001-12-31 17:26 ` Davide Libenzi
2001-12-30 20:47 ` J Sloan
2001-12-30 20:53 ` Davide Libenzi
2001-12-30 21:12 ` Alan Cox
2001-12-30 23:16 ` Stephan von Krawczynski
2002-01-14 1:33 ` Bill Davidsen
-- strict thread matches above, loose matches on Subject: below --
2001-12-29 3:53 Davide Libenzi
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=3C2E4875.9D0F4BC6@zip.com.au \
--to=akpm@zip.com.au \
--cc=Dieter.Nuetzel@hamburg.de \
--cc=davidel@xmailserver.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rml@tech9.net \
/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