From: "Dieter Nützel" <Dieter.Nuetzel@hamburg.de>
To: Ingo Molnar <mingo@elte.hu>
Cc: Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: [patch] O(1) scheduler, 2.4.17-A1, 2.5.2-pre7-A1.
Date: Fri, 4 Jan 2002 23:44:46 +0100 [thread overview]
Message-ID: <20020104224505Z285720-13996+1136@vger.kernel.org> (raw)
In-Reply-To: <Pine.LNX.4.33.0201041238350.2247-100000@localhost.localdomain>
In-Reply-To: <Pine.LNX.4.33.0201041238350.2247-100000@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 1115 bytes --]
On Friday, 4. January 2002 12:42, Ingo Molnar wrote:
> On Fri, 4 Jan 2002, Dieter [iso-8859-15] Nützel wrote:
> > What next? Maybe a combination of O(1) and preempt?
>
> yes, fast preemption of kernel-mode tasks and the scheduler code are
> almost orthogonal. So i agree that to get the best interactive performance
> we need both.
[....]
gcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes
-Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing -fno-common
-pipe -mpreferred-stack-boundary=2 -march=k6 -DEXPORT_SYMTAB -c filemap.c
In file included from filemap.c:26:
/usr/src/linux/include/linux/compiler.h:13: warning: likely' redefined
/usr/src/linux/include/linux/sched.h:445: warning: this is the location of
the previous definition
/usr/src/linux/include/linux/compiler.h:14: warning: unlikely' redefined
/usr/src/linux/include/linux/sched.h:444: warning: this is the location of
the previous definition
But _NO_ fails.
-A2 crash immediatly during first boot.
Second run some crashes and stuck in boot up.
I'll try a clean 2.4.17 + A2 (plus needed ReiserFS stuff), now.
-Dieter
[-- Attachment #2: messages-short.bz2 --]
[-- Type: application/x-bzip2, Size: 3548 bytes --]
[-- Attachment #3: messages-short-ksymoops.bz2 --]
[-- Type: application/x-bzip2, Size: 14889 bytes --]
[-- Attachment #4: boot.omsg.bz2 --]
[-- Type: application/x-bzip2, Size: 2955 bytes --]
next prev parent reply other threads:[~2002-01-04 22:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20020104074239.94E016DAA6@mail.elte.hu>
2002-01-04 11:42 ` [announce] [patch] ultra-scalable O(1) SMP and UP scheduler Ingo Molnar
2002-01-04 22:44 ` Dieter Nützel [this message]
2002-01-05 17:12 ` [patch] O(1) scheduler, 2.4.17-A1, 2.5.2-pre7-A1 Adrian Bunk
2002-01-05 0:28 ` [announce] [patch] ultra-scalable O(1) SMP and UP scheduler Roger Larsson
2002-01-05 7:53 ` george anzinger
2002-01-05 12:42 ` Ingo Molnar
2002-01-05 16:54 ` Robert Love
2002-01-04 17:05 [patch] O(1) scheduler, 2.4.17-A1, 2.5.2-pre7-A1 Ingo Molnar
2002-01-04 17:38 ` Andrey Nekrasov
2002-01-04 19:56 ` Ingo Molnar
2002-01-04 20:19 ` Adrian Bunk
2002-01-04 22:28 ` Ingo Molnar
2002-01-04 21:45 ` Heinz Diehl
2002-01-05 3:41 ` Evgeniy Polyakov
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=20020104224505Z285720-13996+1136@vger.kernel.org \
--to=dieter.nuetzel@hamburg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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®