Re: dual core and c
- From: Antoninus Twink <nospam@xxxxxxxxxxxxxx>
- Date: Fri, 29 Feb 2008 16:55:48 +0100 (CET)
On 29 Feb 2008 at 15:13, kerravon wrote:
Assuming I am running a C program that is doing some cpu-intensive
work
such as zip -9, I can understand:
If I have 8 CPUs, then it will make no difference at all to the zip
program,
it will only run on one of the CPUs, although this does allow me to
run 8
separate zips simultaneously, which would be cool on a large site.
But what I don't understand is the concept of a "core", as in "dual
core".
What implications does that have for a C program like zip? Does it
have the ability to look at the instructions ahead of time and
pipeline
them or something? Pipelining is something that has been around for
a long time. Did someone just get the bright idea to call it dual
core
instead or what?
And HeathField's attack dogs are unleashed in 3... 2... 1...
.
- Follow-Ups:
- Re: dual core and c
- From: Kenny McCormack
- Re: dual core and c
- References:
- dual core and c
- From: kerravon
- dual core and c
- Prev by Date: Re: Is there stack associated when a executing an inline function?
- Next by Date: Re: dual core and c
- Previous by thread: Re: dual core and c
- Next by thread: Re: dual core and c
- Index(es):
Relevant Pages
|