From: "J . A . Magallon" <jamagallon@able.es>
To: Dominik Kubla <dominik.kubla@uni-mainz.de>
Cc: "Michael D . Crawford" <crawford@goingware.com>,
linux-kernel@vger.kernel.org
Subject: Re: How to Power off with ACPI/APM?
Date: Fri, 5 Jan 2001 10:33:06 +0100 [thread overview]
Message-ID: <20010105103306.C2095@werewolf.able.es> (raw)
In-Reply-To: <3A55403C.39E4A48B@goingware.com> <20010105101846.A2095@werewolf.able.es> <20010105102356.B17200@uni-mainz.de>
In-Reply-To: <20010105102356.B17200@uni-mainz.de>; from dominik.kubla@uni-mainz.de on Fri, Jan 05, 2001 at 10:23:56 +0100
On 2001.01.05 Dominik Kubla wrote:
> On Fri, Jan 05, 2001 at 10:18:46AM +0100, J . A . Magallon wrote:
> >
> > Silly question, but have you realized that you don't have to enable
> > SMP in kernel to do multithreading ?
> >
>
> That depends on your definition: If you really want to run multiple
> threads simultaneously (as opposed to concurrent i guess) i imagine
> you will either need more than one CPU or one of those new beasties
> which support multiple threads in parallel on their various execution
> units...
>
Nope. You can run multiple threads "simultaneously" on an uniprocessor,
so simultaneous as the rest of the processes the cpu is running.
Of course the efficiency of multi-threading drops on an uni-processor
if your threads only do hard math work and no IO, but a thread can
be crunchin numbers at the same time one other is waiting for IO even
on a one cpu box. Think on an app that does read-process-write in loop.
Two parallel threads on an uniprocessor can overlap IO and process
and be more efficient than a non-threaded version.
--
J.A. Magallon $> cd pub
mailto:jamagallon@able.es $> more beer
Linux werewolf 2.2.19-pre6 #1 SMP Wed Jan 3 21:28:10 CET 2001 i686
-
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:[~2001-01-05 9:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-05 3:32 How to Power off with ACPI/APM? Michael D. Crawford
2001-01-05 9:18 ` J . A . Magallon
2001-01-05 9:23 ` Dominik Kubla
2001-01-05 9:33 ` J . A . Magallon [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-01-05 18:18 Michael D. Crawford
2001-01-06 3:06 ` idalton
2001-01-05 18:08 Per Jessen
2001-01-05 7:56 Grover, Andrew
2001-01-05 3:00 Michael D. Crawford
2001-01-04 20:26 Michael D. Crawford
2001-01-05 1:10 ` James H. Cloos Jr.
2001-01-05 1:16 ` J . A . Magallon
2001-01-05 1:23 ` J . A . Magallon
2001-01-05 1:33 ` James H. Cloos Jr.
2001-01-05 1:18 ` egger
2001-01-03 20:49 How to power " Michael D. Crawford
2001-01-04 20:09 ` egger
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=20010105103306.C2095@werewolf.able.es \
--to=jamagallon@able.es \
--cc=crawford@goingware.com \
--cc=dominik.kubla@uni-mainz.de \
--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