Access important files from anywhere
AMD helping developers get ready for octo-core
It seems only fair that since the hardware side of the computing world plowed ahead with parallelized computing, they should help out the software development community.
In that spirit, AMD plans to let developers take a crack at its Light-Weight Profiler Tuesday as a possible assist for the growing problem faced by PC software developers: just how the hell are we going to effectively use processors with multiple cores? AMD's LWP could let applications written for runtime environments like Java or .Net interact directly with hardware to know how much performance is available across a series of cores, said Earl Stahl, vice president of software alliances for AMD.
Much has been written about the need for the PC software development community to move past the "free lunch" era, when it could write a single-threaded application and watch its performance improve over time as a processor's clock speed got faster and faster. That ended with the overheating concerns presented by fast single-core chips. Parallel programming is nothing new to the server world, but it's a new path for PC software developers and new techniques are needed to make sure client applications will show improved performance as the number of cores on a chip increases at a faster rate than the actual clock speed of that chip.
LWP is designed to help developers boost the performance of applications created for runtime environments like Java or .NET, such as Web-based applications. Right now, those applications don't talk directly to the processor to see how much performance they've got in the pipeline; they have to go through the operating system. LWP will let that application code see exactly what resources are available, allowing the code to avoid overloaded cache memory in one core, for example, and avoid the performance penalty caused by asking the operating system to query every core.
Right now, this isn't an immediate problem. As we move forward with quad-core chips and eventually to eight cores or more, however, applications will need to know how to allocate themselves across those idle cores, Stahl said. AMD hopes LWP will help a new generation of application development tools make those decisions.
Interested developers can check out the specification on AMD's site, Stahl said. The company's holding the equivalent of a public comment period during which developers can submit feedback for a final specification that could be incorporated into future AMD processors as an extension to the x86 instruction set, such as AMD's 64-bit AMD64 instructions or Intel's SSE multimedia instructions. Eight-core PC chips won't be very common until around the end of this decade at the earliest, giving the industry some time to tackle the problem.
Tom Krazit, a staff writer for CNET News, focuses on all things Apple. He has covered traditional PC companies such as Dell and Hewlett-Packard, chip companies such as Intel and Advanced Micro Devices, and mobile computers ranging from Research In Motion's to Palm's. E-mail Tom.
Multiple processors is a great opportunity that can and should be handled at the OS level. For a start the major OS players should put a load balancer layer and assign processes based on CPU load (the most fundamental and basic approach). The second thing and a bit involving is to load balance at the thread level. This approach requires a bit of effort since you need to define a virtual CPU to manage all the physical CPU registers and give the application the feeling that it's talking to one machine and still have your application executed by differet CPUs.
Copyright 2007 Naumann2007. All rights reserved.
As you probably know, this post wasn't intended as the all-encompassing word on what is being done to help developers get ready for multicore chips.
I also didn't mention that perhaps had Intel and AMD been more prescient about the need for multicore chips in the PC industry, rather than pulling everyone along with the megahertz train for so many years, they could have started the training and educational efforts much earlier and more multithreaded PC applications would have been already developed. Hmm...