Your browser does not support JavaScript!
http://iet.metastore.ingenta.com
1887

Monsters, incapacitated [multicore processors]

Monsters, incapacitated [multicore processors]

For access to this article, please select a purchase option:

Buy article PDF
£12.50
(plus tax if applicable)
Buy Knowledge Pack
10 articles for £75.00
(plus taxes if applicable)

IET members benefit from discounts to all IET publications and free access to E&T Magazine. If you are an IET member, log in to your account and the discounts will automatically be applied.

Learn more about IET membership 

Recommend Title Publication to library

You must fill out fields marked with: *

Librarian details
Name:*
Email:*
Your details
Name:*
Email:*
Department:*
Why are you recommending this title?
Select reason:
 
 
 
 
 
Engineering & Technology — Recommend this title to your library

Thank you

Your recommendation has been sent to your librarian.

The paper discusses the multicore processors. The paper states that multicore processors provide unprecedented compute density, but have wound up being the parts used to scare designers about the future. The arrival of multicore processing in computing and embedded systems has often recalled the marketing for a movie. Indeed, what makes the analogy quite apt is that it may be promised the terrors of the Earth, but reality turns out to be an inoffensive stuntman in a cheaply assembled rubber suit. Consider the two most frequent issues. First, there are those instances where a company wants to consolidate four separate processes that may have each occupied their own printed circuit boards within a system. It wants to bring all these functions onto one piece of silicon for reasons such as power efficiency, size and cost. The second case is that the goals are performance rather than technology driven. Most applications have been coded sequentially, that is they have been written to be executed in a single thread on a single processor or core. In a multicore world, the greatest performance stands to be gained by having a program execute simultaneously across as many cores as are available; the program should be written to be executed in multiple threads in parallel.

http://iet.metastore.ingenta.com/content/journals/10.1049/et.2009.1607
Loading

Related content

content/journals/10.1049/et.2009.1607
pub_keyword,iet_inspecKeyword,pub_concept
6
6
Loading
This is a required field
Please enter a valid email address