From: Jaap-Jan Boor <jjboor@aimsys.nl>
To: Steven Scholz <steven.scholz@imc-berlin.de>
Cc: "linuxppc-embedded@lists.linuxppc.org"
<linuxppc-embedded@lists.linuxppc.org>
Subject: Re: Preemptive Kernel and MPC8xx ???
Date: Mon, 24 Nov 2003 10:46:43 +0100 [thread overview]
Message-ID: <1069667203.31339.146.camel@linpc003.aimsys.nl> (raw)
In-Reply-To: <3FC1BAC8.6030305@imc-berlin.de>
On Mon, 2003-11-24 at 09:01, Steven Scholz wrote:
> Hi,
>
> >> is somebody actually using the preemptive kernel patches ...
> >>
> > Yes I do on 2.4.20 and 2.4.22 from kernel.org. So far all seems
> > to work but didn't do any measurements on it.
> So you're using vanilla 2.4.22 on your MPC8xx board!?
yes, am I stupid?
Currently I use smc uart, scc ethernet and a modified
cpm_spi driver (from the great Denx) with interrupt handling,
my 850 board boots ok from nfsroot
>
> > (I both use the preempt and low-latency patches)
> Sound interessting.
> Could you please give me a link to find the mentioned "low-latency patches".
it comes from Andrew Morton's page
http://www.zip.com.au/~akpm/linux/schedlat.html
I you have to enable this by hand in arch/ppc/config.in (look at
arch/i386/config.in) with
bool 'Low latency scheduling' CONFIG_LOLAT
dep_bool 'Control low latency with sysctl' CONFIG_LOLAT_SYSCTL
$CONFIG_LOLAT
>
> Thanks,
>
> Steven
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-11-24 9:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-23 12:02 Preemptive Kernel and MPC8xx ??? Steven Scholz
2003-11-24 7:20 ` Jaap-Jan Boor
2003-11-24 8:01 ` Steven Scholz
2003-11-24 9:46 ` Jaap-Jan Boor [this message]
2003-11-24 9:55 ` Steven Scholz
2003-11-24 16:35 ` Marius Groeger
2003-11-24 22:33 ` Jaap-Jan Boor
2003-11-25 8:13 ` Steven Scholz
2003-11-26 16:19 ` Jaap-Jan Boor
2003-11-26 15:08 ` Steven Scholz
2003-11-26 16:23 ` Jaap-Jan Boor
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=1069667203.31339.146.camel@linpc003.aimsys.nl \
--to=jjboor@aimsys.nl \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=steven.scholz@imc-berlin.de \
/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.