From: LA Walsh <law@sgi.com>
To: linux-kernel@vger.kernel.org
Subject: Power usage Q and parallel make question (separate issues)
Date: Wed, 31 Jan 2001 11:44:28 -0800 [thread overview]
Message-ID: <3A786B1C.F6A3CE83@sgi.com> (raw)
I remember reading some time back that on a pentium the difference between a
pentium in HLT vs. running was about 2-3 watts vs. 15-20 watts. Does anyone
know the difference for today's CPU's? P-III/P-IV or other archs?
How about the difference when calling the BIOS power-save feature? With
the threat of rolling blackouts here in CA, I was wondering what the power
consumption might be of a 100,000 or 1,000,000 CPU's in HLT vs. doing complex
mathematical computation?
Separately -- Parallel Make's
---------- ===============
So, just about anyone I know uses make -j X [-l Y] bzImage modules, but I noticed that
make modules_install isn't parallel safe in 2.4 -- since it takes much longer than the
old, it would make sense to want to run it in parallel as well, but it has a
delete-old, <multiple sub-dirs>, index-new for deps. Those "3" steps can't be done
in parallel safely. Was this intentional or would a 'fix' be desired?
Is it the intention of the Makefile maintainers to allow a parallel or distributed
make? I know for me it makes a noticable difference even on a 1 CPU machine
(CPU overlap with disk I/O), and with multi CPU machines, it's even more noticable.
Is a make of the kernel and/or the modules designed to be parallel safe? Is it
something I should 'rely' on? If it isn't, should it be?
-l
--
Linda A Walsh | Trust Technology, Core Linux, SGI
law@sgi.com | Voice: (650) 933-5338
-
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 reply other threads:[~2001-01-31 19:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-31 19:44 LA Walsh [this message]
2001-02-01 0:32 ` Power usage Q and parallel make question (separate issues) Keith Owens
2001-02-01 3:02 ` LA Walsh
2001-02-01 3:32 ` Keith Owens
2001-02-01 8:13 ` LA Walsh
2001-02-01 8:24 ` Keith Owens
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=3A786B1C.F6A3CE83@sgi.com \
--to=law@sgi.com \
--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