From: Con Kolivas <conman@kolivas.net>
To: dmarkh@cfl.rr.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Combined low latency & performance patches for 2.4.18
Date: Thu, 2 May 2002 07:07:36 +1000 [thread overview]
Message-ID: <20020501210737.3C40218A8C@pc.kolivas.net> (raw)
In-Reply-To: <20020429142443.A62481333@pc.kolivas.net> <20020430230105.D5CA01A0AA@pc.kolivas.net> <3CCFA3BD.664EE747@cfl.rr.com>
Mark
On Wed, 1 May 2002 18:13, you wrote:
> Con Kolivas wrote:
> > On Tue, 30 Apr 2002 02:51, you wrote:
> > > After applying it, if you ever do a make mrproper oldconfig dep bzImage
> > > it fails to compile sched.c as follows
> > >
> > > If I don't do an mrproper it compiles ok. Haven't tested yet.
> >
> > Hmm
> > I used a make mrproper && make clean followed by manual configuration
> > without any problems but thanks for your input. I'm not claiming to be a
> > patch or kernel guru. Just offering what worked for me.
> >
> > > It's the O1 sched patch. Not your fault....
> >
> > Thanks thats kinda reassuring :)
> >
> > Con.
>
> I take that back. It's the low-latency patch. You must have said no to
> it in your .config.
> I do not think all these patches play well together with the O(1)
Here is the relevant section from my .config:
# Processor type and features
#
CONFIG_LOLAT=y
# CONFIG_LOLAT_SYSCTL is not set
CONFIG_PREEMPT=y
As you can see, the low latency is enabled. I didn't see any point in
enabling sysctl so I havent tried that. Perhaps that is it? The other thing
is, I don't believe it works well with SMP which I am not using.
Con.
next prev parent reply other threads:[~2002-05-01 21:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-29 14:24 Con Kolivas
[not found] ` <3CCD7A07.D661110E@compro.net>
2002-04-30 23:01 ` Con Kolivas
2002-05-01 8:13 ` Mark Hounschell
2002-05-01 21:07 ` Con Kolivas [this message]
2002-05-14 13:42 ` Con Kolivas
2002-05-14 13:54 ` Mark Hounschell
2002-05-14 14:17 ` Con Kolivas
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=20020501210737.3C40218A8C@pc.kolivas.net \
--to=conman@kolivas.net \
--cc=dmarkh@cfl.rr.com \
--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
all inboxes | Powered by JetHome®