From: "Jeff V. Merkey" <jmerkey@vger.timpanogas.org>
To: "Richard B. Johnson" <root@chaos.analogic.com>
Cc: "Jeff V. Merkey" <jmerkey@timpanogas.org>,
Keith Owens <kaos@ocs.com.au>,
linux-kernel@vger.kernel.org
Subject: Re: Dual XEON - >>SLOW<< on SMP
Date: Wed, 8 Nov 2000 12:17:32 -0700 [thread overview]
Message-ID: <20001108121732.C11377@vger.timpanogas.org> (raw)
In-Reply-To: <3A088A3D.2CD0BC53@timpanogas.org> <Pine.LNX.3.95.1001108091850.258A-100000@chaos.analogic.com>
In-Reply-To: <Pine.LNX.3.95.1001108091850.258A-100000@chaos.analogic.com>; from root@chaos.analogic.com on Wed, Nov 08, 2000 at 09:28:54AM -0500
On Wed, Nov 08, 2000 at 09:28:54AM -0500, Richard B. Johnson wrote:
> On Tue, 7 Nov 2000, Jeff V. Merkey wrote:
>
> >
> > Marc Lehman verified that PII systems will generate tons of AGIs with
> > gcc. Perhaps this is the cause of this problem. You could run EMON and
> > see if there is something obvious in the numbers ...
> >
> > Jeff
> >
>
> Here are some tests:
>
> Before the tests, I do:
> `ifconfig eth0 down`
> `kill -TERM -1`
>
> Then I disconnect my ethernet cable to get rid of those interrupts.
>
>
> This is the test-script:
> make clean
> time make -j 10 bzImage
>
> It is executed as `sh test.sh &>World.Log &` .
>
>
> This is Linux 2.4.0-test9
>
> This is a kernel build with NMI watchdog turned OFF:
> 349.04user 19.83system 3:21.96elapsed 182%CPU (0avgtext+0avgdata 0maxresident)k
> 0inputs+0outputs (0major+0minor)pagefaults 0swaps
>
>
> This is a kernel build with NMI watchdog turned ON:
> 348.23user 18.84system 3:57.14elapsed 154%CPU (0avgtext+0avgdata 0maxresident)k
> 0inputs+0outputs (0major+0minor)pagefaults 0swaps
>
> The elapsed time went from 3:21 to 3:57.
>
>
> This is Linux 2.2.17
>
> This is the kernel build (the exact same build as above).
> 214.91user 12.93system 2:37.00elapsed 145%CPU (0avgtext+0avgdata 0maxresident)k
> 0inputs+0outputs (0major+0minor)pagefaults 0swaps
>
> The original elapsed time when booting 2.2.17 was 2:37. It is now 3:57.
>
> This is, in every case, rebuilding the exact same kernel.
>
> It doth appearith asthough ithsucks.
>
I'll attempt to reproduce. I've got live internet servers running on 2.2.18-19
and am not seeing this.
Jeff
>
> Cheers,
> Dick Johnson
>
> Penguin : Linux version 2.4.0 on an i686 machine (799.54 BogoMips).
>
> "Memory is like gasoline. You use it up when you are running. Of
> course you get it all back when you reboot..."; Actual explanation
> obtained from the Micro$oft help desk.
>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-08 18:22 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-02 13:50 Dual XEON - >>SLOW<< on SMP Dr. David Gilbert
2000-11-02 13:56 ` kernel
2000-11-02 14:02 ` Richard B. Johnson
2000-11-02 18:09 ` Ulrich Drepper
2000-11-02 18:23 ` Maciej W. Rozycki
2000-11-02 18:26 ` Matti Aarnio
2000-11-02 18:38 ` Chris Meadors
2000-11-02 18:40 ` Richard B. Johnson
2000-11-02 23:39 ` Wakko Warner
2000-11-07 22:02 ` Dr. Kelsey Hudson
2000-11-07 22:10 ` Jan-Benedict Glaw
2000-11-07 22:16 ` kernel
2000-11-07 22:31 ` Richard B. Johnson
2000-11-07 22:41 ` Keith Owens
2000-11-07 22:55 ` Richard B. Johnson
2000-11-07 23:03 ` Jeff V. Merkey
2000-11-08 14:28 ` Richard B. Johnson
2000-11-08 19:17 ` Jeff V. Merkey [this message]
2000-11-11 19:26 ` Marc Lehmann
2000-11-13 6:22 ` Jeff V. Merkey
2000-11-13 8:41 ` James A. Sutherland
2000-11-13 11:51 ` Marc Lehmann
2000-11-07 22:48 ` J . A . Magallon
2000-11-02 14:10 ` Tigran Aivazian
2000-11-02 17:39 ` Dr. David Gilbert
2000-11-03 0:04 ` bert hubert
2000-11-03 16:13 ` Ricky Beam
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=20001108121732.C11377@vger.timpanogas.org \
--to=jmerkey@vger.timpanogas.org \
--cc=jmerkey@timpanogas.org \
--cc=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=root@chaos.analogic.com \
/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