mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: jjs@pobox.com (J Sloan)
Cc: timothy.covell@ashavan.org,
	skraw@ithnet.com (Stephan von Krawczynski),
	davidel@xmailserver.org (Davide Libenzi),
	Dieter.Nuetzel@hamburg.de (Dieter Nützel),
	rml@tech9.net (Robert Love),
	linux-kernel@vger.kernel.org (Linux Kernel List)
Subject: Re: [PATCH] Balanced Multi Queue Scheduler ...
Date: Sun, 30 Dec 2001 21:12:51 +0000 (GMT)	[thread overview]
Message-ID: <E16KnGF-0002WU-00@the-village.bc.nu> (raw)
In-Reply-To: <3C2F7D49.9040606@pobox.com> from "J Sloan" at Dec 30, 2001 12:47:05 PM

> On my 4-way ppro, make -j4 is much faster
> than a simple "make" for kernel compilation.
> Almost linearly so -

Make does lots of I/O and also has lots of stuff that can run in parallel
and balance out easily. The real test case for you to try are 5, 6, 7, and 8
copies of seti

  parent reply	other threads:[~2001-12-30 21:03 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-29  5:16 Dieter Nützel
2001-12-29 22:29 ` Davide Libenzi
2001-12-29 22:49   ` Andrew Morton
2001-12-29 23:39     ` Davide Libenzi
2001-12-29 23:38   ` Stephan von Krawczynski
2001-12-30  0:02     ` Davide Libenzi
2001-12-30  2:32     ` Alan Cox
2001-12-30  3:11       ` Dieter Nützel
2001-12-30 19:47     ` Timothy Covell
2001-12-30 20:16       ` Davide Libenzi
2001-12-30 23:20         ` Stephan von Krawczynski
2001-12-30 23:46           ` Davide Libenzi
2001-12-31 16:37           ` Stephan von Krawczynski
2001-12-31 17:26             ` Davide Libenzi
2001-12-30 20:47       ` J Sloan
2001-12-30 20:53         ` Davide Libenzi
2001-12-30 21:12         ` Alan Cox [this message]
2001-12-30 23:16       ` Stephan von Krawczynski
2002-01-14  1:33       ` Bill Davidsen
  -- strict thread matches above, loose matches on Subject: below --
2001-12-29  3:53 Davide Libenzi

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=E16KnGF-0002WU-00@the-village.bc.nu \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=Dieter.Nuetzel@hamburg.de \
    --cc=davidel@xmailserver.org \
    --cc=jjs@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rml@tech9.net \
    --cc=skraw@ithnet.com \
    --cc=timothy.covell@ashavan.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®