From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: lkml <linux-kernel@vger.kernel.org>
Subject: Re: [BUG] 2.6.0-test2 loses time on 486
Date: Thu, 31 Jul 2003 08:06:59 +0200 [thread overview]
Message-ID: <20030731060659.GK1873@lug-owl.de> (raw)
In-Reply-To: <1059607019.14771.117.camel@w-jstultz2.beaverton.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 1112 bytes --]
On Wed, 2003-07-30 16:16:59 -0700, john stultz <johnstul@us.ibm.com>
wrote in message <1059607019.14771.117.camel@w-jstultz2.beaverton.ibm.com>:
> On Wed, 2003-07-30 at 15:52, Mikael Pettersson wrote:
> > On 30 Jul 2003 13:08:44 -0700, john stultz <johnstul@us.ibm.com> wrote:
> Regardless, as you've demonstrated, it seems 486s just can't keep up w/
> HZ=1000. Maybe we need to look into some sort of processor specific HZ
> config option?
I'd like to see that. Eventually, I'll post some patch to do that, but
first, I need to make Debian to support i386 again (since libstdc++5 in
unstable is now compiled for i486, some apps (apt-get is one of
those...) will SIGILLed to death). I do have some of those boxes (Am386
with SIMM RAM, i386SX-16 with SIPP modules + single ICs :)
MfG, JBG
--
Jan-Benedict Glaw jbglaw@lug-owl.de . +49-172-7608481
"Eine Freie Meinung in einem Freien Kopf | Gegen Zensur | Gegen Krieg
fuer einen Freien Staat voll Freier Bürger" | im Internet! | im Irak!
ret = do_actions((curr | FREE_SPEECH) & ~(IRAQ_WAR_2 | DRM | TCPA));
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-07-31 6:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-30 22:52 Mikael Pettersson
2003-07-30 23:16 ` john stultz
2003-07-31 6:06 ` Jan-Benedict Glaw [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-07-30 19:19 Mikael Pettersson
2003-07-30 20:08 ` john stultz
2003-07-29 17:34 Mikael Pettersson
2003-07-29 18:59 ` john stultz
2003-07-29 19:15 ` Sean Estabrooks
2003-07-29 21:47 ` Frank van Maarseveen
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=20030731060659.GK1873@lug-owl.de \
--to=jbglaw@lug-owl.de \
--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®