public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Daniel Egger <degger@fhm.edu>
To: mingo@elte.hu
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Performance of Ingo's O(1) scheduler on NUMA-Q
Date: 08 Feb 2002 16:15:56 +0100	[thread overview]
Message-ID: <1013181364.31423.9.camel@sonja> (raw)
In-Reply-To: <Pine.LNX.4.33.0202080021520.7544-100000@localhost.localdomain>
In-Reply-To: <Pine.LNX.4.33.0202080021520.7544-100000@localhost.localdomain>

Am Fre, 2002-02-08 um 00.23 schrieb Ingo Molnar:

> > Measuring kernel compile times on a 16 way NUMA-Q, adding Ingo's
> > scheduler patch takes kernel compiles down from 47 seconds to 31
> > seconds .... pretty impressive benefit.
 
> cool! By the way, could you try a test-compile with a 'big' .config file?

I'd assume that a 16way machine still taking 31s to compile the kernel
is already having a 'big' config file. 
 
-- 
Servus,
       Daniel


  reply	other threads:[~2002-02-09 17:08 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-21 15:05 [patch] O(1) scheduler, -J4 Ingo Molnar
2002-01-21 15:32 ` [patch] O(1) scheduler, -J4, 2.4.18-pre4 Ingo Molnar
2002-01-24  1:43   ` Ingo's O(1) scheduler vs. wait_init_idle Martin J. Bligh
2002-01-24  9:21     ` Ingo Molnar
2002-01-24 17:47       ` Martin J. Bligh
2002-01-24 19:59         ` Ingo Molnar
2002-01-26 17:19         ` Jesse Barnes
2002-01-25 23:07     ` Performance of Ingo's O(1) scheduler on 8 way NUMA-Q Martin J. Bligh
2002-02-07 13:08       ` Performance of Ingo's O(1) scheduler on NUMA-Q Martin J. Bligh
2002-02-07 23:23         ` Ingo Molnar
2002-02-08 15:15           ` Daniel Egger [this message]
2002-02-11 17:39             ` Martin J. Bligh

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=1013181364.31423.9.camel@sonja \
    --to=degger@fhm.edu \
    --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