From: Jaap-Jan Boor <jjboor@aimsys•nl>
To: Steven Scholz <steven.scholz@imc-berlin•de>
Cc: Marius Groeger <mgroeger@sysgo•com>,
"linuxppc-embedded@lists•linuxppc.org"
<linuxppc-embedded@lists•linuxppc.org>
Subject: Re: Preemptive Kernel and MPC8xx ???
Date: Wed, 26 Nov 2003 17:23:06 +0100 [thread overview]
Message-ID: <1069863786.1263.6.camel@linpc003.aimsys.nl> (raw)
In-Reply-To: <3FC4C1DD.3020209@imc-berlin.de>
On Wed, 2003-11-26 at 16:08, Steven Scholz wrote:
> Marius Groeger wrote:
>
> > AFAIK, you can pretty much drop the low-latency patch in favor of
> > using the lock-breaking patch. It is also available from Robert Love
> > at the cited home page.
>
> Rob Love wrote me:
>
> >>Is it correct that your lock-break does basicly the same as Andrew Morton's
> >>low-latency patches? Where is the big difference?
> >
> > Yes, basically the same thing. Lock-break is a version of low-latency
> > that is "optimized" for use with the preemptive kernel.
> >
> > You might as well just use low-latency, as Andrew is keeping that more
> > up to date.
>
> And that's what I noticed when looking and the download pages...
>
> That leaves three options:
>
> > (a) Use only preempt-kernel
> > (b) Use only low-latency
> > (c) Use preempt-kernel + low-latency
>
> Right?
Yes, I use (c)
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2003-11-26 16:23 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
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 [this message]
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=1069863786.1263.6.camel@linpc003.aimsys.nl \
--to=jjboor@aimsys$(echo .)nl \
--cc=linuxppc-embedded@lists$(echo .)linuxppc.org \
--cc=mgroeger@sysgo$(echo .)com \
--cc=steven.scholz@imc-berlin$(echo .)de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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