From: "Dieter Nützel" <Dieter.Nuetzel@hamburg.de>
To: "J.A. Magallon" <jamagallon@able.es>
Cc: Linux Kernel List <linux-kernel@vger.kernel.org>,
"Martin J. Bligh" <Martin.Bligh@us.ibm.com>,
Ingo Molnar <mingo@redhat.com>, Robert Love <rml@tech9.net>,
George Anzinger <george@mvista.com>,
Andrew Morton <akpm@zip.com.au>
Subject: Re: 0(1)-patch, where did it go?
Date: Thu, 11 Apr 2002 05:27:35 +0200 [thread overview]
Message-ID: <200204110527.35486.Dieter.Nuetzel@hamburg.de> (raw)
> You can get an up-to-date version in the 2.4.19-pre6-jam1 patcset in
>
> http://giga.cps.unizar.es/~magallon/linux/kernel/
Didn't you noticed any of the reports about very bad numbers for latency since
Ingo's latest 2.4.17-K3 version?
Even Alan's tree show the same (latest I've checked was 2.4.19-pre2-ac2).
We do need some words from Ingo first.
He haven't answered my posts since February ;-(
But yaybe he didn't got them 'cause I send them to mingo@elte.hu ???
If you run without O(1) latency is like before.
You'll get better numbers with preemption+lock-break (ongoing merge of
Andrew's lowlatency patches).
But I see some kernel hangs with preemption on UP.
It happens only during "make bzlilo" (the linking stage). Robert?
Apart from that it works well.
-Dieter
--
Dieter Nützel
Graduate Student, Computer Science
University of Hamburg
Department of Computer Science
@home: Dieter.Nuetzel@hamburg.de
next reply other threads:[~2002-04-11 3:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-11 3:27 Dieter Nützel [this message]
2002-04-11 3:30 ` Robert Love
2002-04-11 3:44 ` Dieter Nützel
2002-04-11 5:58 ` KELEMEN Peter
-- strict thread matches above, loose matches on Subject: below --
2002-04-09 20:51 listmail
2002-04-09 21:11 ` J Sloan
2002-04-09 22:16 ` J.A. Magallon
2002-04-10 5:34 ` Martin J. Bligh
2002-04-10 21:49 ` J.A. Magallon
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=200204110527.35486.Dieter.Nuetzel@hamburg.de \
--to=dieter.nuetzel@hamburg.de \
--cc=Martin.Bligh@us.ibm.com \
--cc=akpm@zip.com.au \
--cc=george@mvista.com \
--cc=jamagallon@able.es \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rml@tech9.net \
/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®