From: William Lee Irwin III <wli@holomorphy.com>
To: Christian Meder <chris@onestepahead.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6 vs 2.4 regression when running gnomemeeting
Date: Fri, 19 Dec 2003 12:32:27 -0800 [thread overview]
Message-ID: <20031219203227.GR31393@holomorphy.com> (raw)
In-Reply-To: <1071864709.1044.172.camel@localhost>
On Fri, Dec 19, 2003 at 09:11:50PM +0100, Christian Meder wrote:
> I've got a longstanding regression in gnomemeeting usage when switching
> between 2.4 and 2.6 kernels.
> Phenomenon:
> Without load gnomemeeting VOIP connections are fine. As soon as some
> load like a kernel compile is put on the laptop the gnomemeeting audio
> stream is cut to pieces and gets unintelligible . On 2.4.2x I don't get
> even the slightest distortion in the audio stream under load. I played
> around with different nice levels with no success. The problem persisted
> during the whole 2.6.0-test series no matter whether I used -mm kernels
> or pristine Linus kernels. Even when nicing the kernel compile to +19
> the distortions start right away. I tried Nick Piggin's scheduler which
> fared slightly better after changing the nice level of gnomemeeting to
> -10 but it's still a far cry from the 2.4.2x feeling without any
> fiddling with nice values.
> Any hints where to start looking are greatly appreciated.
Please instrument your workload with the following, and send logs of the
output (preferably compressed) to me and possibly others:
top b d 5
vmstat 5
while true; do cat /proc/vmstat; sleep 5; done
while true; do cat /proc/meminfo; sleep 5; done
A good way to log commands like this is:
(command) > /home/foo.log.1 2>&1 &
where parentheses surround the command in the actual shell input.
-- wli
next prev parent reply other threads:[~2003-12-19 20:32 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 [this message]
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
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=20031219203227.GR31393@holomorphy.com \
--to=wli@holomorphy.com \
--cc=chris@onestepahead.de \
--cc=linux-kernel@vger.kernel.org \
/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