From: Mike Galbraith <efault@gmx.de>
To: Con Kolivas <kernel@kolivas.org>
Cc: Martin Schlemmer <azarah@gentoo.org>,
Nick Piggin <piggin@cyberone.com.au>,
linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH]O14int
Date: Mon, 11 Aug 2003 18:31:09 +0200 [thread overview]
Message-ID: <5.2.1.1.2.20030811181759.019ffcf0@pop.gmx.net> (raw)
In-Reply-To: <200308120033.32391.kernel@kolivas.org>
At 12:33 AM 8/12/2003 +1000, Con Kolivas wrote:
>I'm trying to work on it I hope you can report exactly what your issue is and
>I'll try and address it. Do you really compile jobs make -j10 each time while
>using your machine? (rhetoric question of course since there is absolutely no
>advantage to doing that without lots of cpus). If not, how does it perform
>under your real world conditions?
Um, slight ~objection.
What's the difference between one tester running a make -j10 and 10
students compiling their assignments in a multiuser box? I test throughput
with make -j30 on a 128Mb 500Mhz PIII, because I know for a very very many
times measured fact that the box can handle this (heavy but _not_ extreme)
load. It's not the only load in the world, but it's such a dead simple
load that the kernel dare not have difficulty with it IMHO.
-Mike
next prev parent reply other threads:[~2003-08-11 16:29 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-08 15:49 [PATCH]O14int Con Kolivas
2003-08-08 17:57 ` [PATCH]O14int Timothy Miller
2003-08-09 0:44 ` [PATCH]O14int Con Kolivas
2003-08-08 19:31 ` [PATCH]O14int Felipe Alfaro Solana
2003-08-09 9:04 ` [PATCH]O14int Con Kolivas
2003-08-11 5:44 ` [PATCH]O14int Martin Schlemmer
2003-08-11 6:08 ` [PATCH]O14int Con Kolivas
2003-08-11 8:35 ` [PATCH]O14int Martin Schlemmer
2003-08-11 8:37 ` [PATCH]O14int Zwane Mwaikambo
2003-08-11 9:07 ` [PATCH]O14int Con Kolivas
2003-08-11 9:15 ` [PATCH]O14int Nick Piggin
2003-08-11 9:43 ` [PATCH]O14int Con Kolivas
2003-08-11 9:44 ` [PATCH]O14int Nick Piggin
2003-08-11 14:04 ` [PATCH]O14int Martin Schlemmer
2003-08-11 14:33 ` [PATCH]O14int Con Kolivas
2003-08-11 15:19 ` [PATCH]O14int Martin Schlemmer
2003-08-13 6:48 ` [PATCH]O14int Con Kolivas
2003-08-14 6:19 ` [PATCH]O14int William Lee Irwin III
2003-08-15 23:40 ` [PATCH]O14int Paul Dickson
2003-08-17 2:20 ` [PATCH]O14int William Lee Irwin III
2003-08-11 16:31 ` Mike Galbraith [this message]
2003-08-11 23:54 ` [PATCH]O14int Timothy Miller
2003-08-11 13:58 ` [PATCH]O14int Martin Schlemmer
2003-08-11 17:55 ` [PATCH]O14int William Lee Irwin III
2003-08-08 20:08 [PATCH]O14int Voluspa
2003-08-09 0:36 ` [PATCH]O14int Con Kolivas
2003-08-10 8:48 ` [PATCH]O14int Simon Kirby
2003-08-10 9:06 ` [PATCH]O14int Con Kolivas
2003-08-12 17:56 ` [PATCH]O14int Simon Kirby
2003-08-12 21:21 ` [PATCH]O14int Con Kolivas
2003-08-10 10:08 ` [PATCH]O14int William Lee Irwin III
2003-08-12 18:36 ` [PATCH]O14int Simon Kirby
2003-08-10 11:17 ` [PATCH]O14int Mike Galbraith
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=5.2.1.1.2.20030811181759.019ffcf0@pop.gmx.net \
--to=efault@gmx.de \
--cc=azarah@gentoo.org \
--cc=kernel@kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=piggin@cyberone.com.au \
/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;
as well as URLs for NNTP newsgroup(s).