From: xenophile <xenophile@domain.hid>
To: xenomai@xenomai.org
Subject: [Xenomai-help] linux 2.6.11
Date: Sat, 21 Apr 2012 22:12:06 +0200 [thread overview]
Message-ID: <4F931496.1060607@domain.hid> (raw)
In-Reply-To: <mailman.0.1334997334.18156.xenomai@xenomai.org>
Hi,
I am trying to see why a trivial driver reading an ADC on an EP9312 ARM
board has slowed by a factor of three. Since I installed it under 2.6.29
a couple fo years ago.
It's looking like this is due to a kernel update I did in the mean time
to 2.6.32
I have just built a new toolchain and rebuilt the kernel to 2.6.33 and
the result is about the same.
I recall a number of years ago running a 2.6.11 kernel and the system
was incredibily responsive. I could be building kde-libs, downloading at
full speed browsing and listening to mp3 decoded music all without the
slightest lack of responsiveness in the browser not a glitch in the mp3
playback.
It was truly impressive.
Now I find if I am rebuilding the toolchain , the browser or any other
window can take over a second to respond to a redraw ( 2.6.32 on this
machine).
Now I've seen comments on audio forums that there was nothing better
than linux 2.6.11 for real time audio work. I'm wondering whether there
is not a general degradation in the linux kernel as time goes on. It
certainly seems to be getting forever bigger and slower.
Would there be any value in trying to rebuild a 2.6.11 based system for
realtime work ?
TIA,
next parent reply other threads:[~2012-04-21 20:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.0.1334997334.18156.xenomai@xenomai.org>
2012-04-21 20:12 ` xenophile [this message]
2012-04-21 21:03 ` [Xenomai-help] linux 2.6.11 Gilles Chanteperdrix
2012-04-22 6:23 ` xenophile
2012-04-22 11:22 ` Gilles Chanteperdrix
2012-04-22 9:10 ` Wolfgang Grandegger
2012-04-22 11:24 ` Gilles Chanteperdrix
2012-04-22 11:34 ` Gilles Chanteperdrix
2012-04-22 13:53 ` Wolfgang Grandegger
2012-04-22 14:02 ` Gilles Chanteperdrix
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=4F931496.1060607@domain.hid \
--to=xenophile@domain.hid \
--cc=xenomai@xenomai.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 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.