From: Christian Meder <chris@onestepahead.de>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6 vs 2.4 regression when running gnomemeeting
Date: Sat, 20 Dec 2003 17:17:21 +0100 [thread overview]
Message-ID: <1071937040.1025.27.camel@localhost> (raw)
In-Reply-To: <20031220111917.GA18267@elte.hu>
On Sat, 2003-12-20 at 12:19, Ingo Molnar wrote:
> * Christian Meder <chris@onestepahead.de> wrote:
>
> > That would leave me with two possibilities: 2.6. is doing something
> > different in the gnomemeeting case or gnomemeeting is doing something
> > different in the 2.6 case. A cursory look at the gnomemeeting sources
> > didn't give me the impression that it's doing anything which would be
> > affected by 2.6 deployment but I'll ask on the gnomemeeting-devel list
> > for advice.
>
> yep, i've looked at the source too and it doesnt do anything that
> changed in 2.6 from an interactivity POV.
>
> To analyze the precise workload that hurts gnomemeeting, could you try
> the following workload:
>
> main()
> {
> for (;;) sched_yield();
> }
>
> and run 1-2 copies of such a load-generator - does it degrade
> gnome-meeting audio just as much as eg. a kernel compile does?
>
> as a next step, does the following degrade gnomemeeting?:
>
> main()
> {
> for (;;) ;
> }
>
> my guess would be that if the yield() one degrades interactivity too
> then this is unlikely to be somehow related to the scheduler proper.
>
> If it doesnt degrade but the simple non-yield loop above does, then it's
> probably something scheduling related in the sound architecture. (eg.
> use of yield() by some codepath of the sound drivers - although they
> dont seem to be doing anything like this.)
>
> If neither of these workloads degrades gnomemeeting, but a kernel-make
> does, then it's the interactivity estimator.
Ok, the results are in. Running up to three yield-loops doesn't degrade
gnomemeeting. Running one non-yield loop does degrade gnomemeeting
_very_ slightly. Adding a second non-yield loop has approximately the
same stuttering effect as a kernel compile. Adding a third non-yield
loop makes gnomemeeting totally unusable.
All these tests were done with Nick's scheduler patch. If I should retry
with stock 2.6.0 just tell me.
Sound driver is by the way snd_es1968 in ALSA and maestro in OSS.
Christian
--
Christian Meder, email: chris@onestepahead.de
What's the railroad to me ?
I never go to see
Where it ends.
It fills a few hollows,
And makes banks for the swallows,
It sets the sand a-blowing,
And the blackberries a-growing.
(Henry David Thoreau)
next prev parent reply other threads:[~2003-12-20 16:17 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-19 20:11 2.6 vs 2.4 regression when running gnomemeeting Christian Meder
2003-12-19 20:32 ` William Lee Irwin III
2003-12-19 23:30 ` Christian Meder
2003-12-20 0:21 ` Nick Piggin
2003-12-20 0:37 ` Christian Meder
2003-12-20 0:48 ` Nick Piggin
2003-12-20 1:11 ` Christian Meder
2003-12-20 1:26 ` Nick Piggin
2003-12-20 1:52 ` Christian Meder
2003-12-20 2:38 ` Nick Piggin
2003-12-20 2:55 ` Con Kolivas
2003-12-20 3:32 ` Christian Meder
2003-12-20 3:50 ` Nick Piggin
2003-12-20 4:16 ` Christian Meder
2003-12-20 4:32 ` Nick Piggin
2003-12-20 5:15 ` Christian Meder
2003-12-20 8:31 ` Con Kolivas
2003-12-20 11:19 ` Ingo Molnar
2003-12-20 16:17 ` Christian Meder [this message]
2003-12-20 16:49 ` Christian Meder
2003-12-20 17:42 ` Ingo Molnar
2003-12-21 1:40 ` Christian Meder
2003-12-21 8:57 ` Ingo Molnar
2003-12-22 1:19 ` Christian Meder
2003-12-22 1:47 ` Con Kolivas
2003-12-22 8:48 ` Ingo Molnar
2003-12-20 23:29 ` Nick Piggin
2003-12-20 22:20 ` Matthias Andree
2003-12-21 19:23 ` Jens Axboe
2003-12-22 10:54 ` Andrew McGregor
2003-12-22 11:15 ` Con Kolivas
2003-12-22 12:51 ` Ingo Molnar
2003-12-22 13:25 ` Nick Piggin
2003-12-20 19:34 ` Marc Schiffbauer
2003-12-21 1:49 ` Christian Meder
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=1071937040.1025.27.camel@localhost \
--to=chris@onestepahead.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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.