Language Selection

English French German Italian Portuguese Spanish

NVIDIA graphics drivers to go multithreaded

Filed under
Software spoke recently with Ben de Waal, NVIDIA's Vice President of GPU software, and he revealed that NVIDIA has plans to produce multithreaded ForceWare graphics drivers for its GeForce graphics products.

Multithreading in the video driver should allow performance increases when running 3D games and applications on dual-core CPUs and multiprocessor PCs. De Waal estimated that dual-core processors could see performance boosts somewhere between five and 30% with these drivers.

Most imminent on the horizon right now is ForceWare release 75, which will bring a number of improvements for SLI performance and 64-bit Windows, among other things, but release 75 will not be multithreaded. The next major iteration of the driver, release 80, is slated to bring support for multiple threads. We may not see this version for a few months; NVIDIA hasn't given an exact timetable for the completion of release 80.

Out of curiosity, I asked de Waal why NVIDIA's drivers don't already take advantage of a second CPU. After all, the driver is a separate task from the application calling it, and Hyper-Threaded and SMP systems are rather common. He explained that drivers in Windows normally run synchronously with the applications making API calls, so that they must return an answer before the API call is complete. On top of that, Windows drivers run in kernel mode, so the OS isn't particularly amenable to multithreaded drivers. NVIDIA has apparently been working on multithreaded drivers for some time now, and they've found a way to fudge around the OS limitations.

De Waal cited several opportunities for driver performance gains with multithreading. Among them: vertex processing. He noted that NVIDIA's drivers currently do load balancing for vertex processing, offloading some work to the CPU when the GPU is busy. This sort of vertex processing load could be spun off into a separate thread and processed in parallel.

Some of the driver's other functions don't lend themselves so readily to parallel threading, so NVIDIA will use a combination of fully parallel threads and linear pipelining. We've seen the benefits of linear pipelining in our LAME audio encoding tests; this technique uses a simple buffering scheme to split work between two threads without creating the synchronization headaches of more parallel threading techniques.

Despite the apparent gains offered by multithreading, de Waal expressed some skepticism about the prospects for thread-level parallelism for CPUs. He was concerned that multithreaded games could blunt the impact of multithreaded graphics drivers, among other things.


More in Tux Machines

ARTIK is the Tizen’s Trojan Horse to dominate the IoT ecosystem

As part of the Forum “Tizen for the Internet of Things” held on September 22 in Moscow, Samsung Electronics has presented a new family of maker boards and modules named ARTIK, in addition to the infrastructure of the operating system Tizen 3.0. Samsung ARTIK’s value proposition, as declared by Samsung, is to reinvent the prototyping process by leveraging world-class data security granted by the company as well as a wide array of tools, both hardware and software, such as the ARTIK Modules and Cloud, formerly known as SmartThings Open Cloud. Read more

today's leftovers

today's howtos

Android Leftovers

  • Google Pixel review: The best Android phone, even if it is a little pricey
    Welcome to the age of Google Hardware. Apparently tired of letting third-party Android OEMs serve as the stewards of Android handsets, Google has become a hardware company. (Again). Earlier this year Google, launched a hardware division with former Motorola President Rick Osterloh at the helm. With the high-ranking title of "Senior Vice President," Osterloh doesn't oversee a side project—his group is on even footing with Android, Search, YouTube, and Ads. The hardware group is so powerful inside Google that it was able to merge Nexus, Pixel, Chromecast, OnHub, ATAP, and Glass into a single business unit. The group's coming out party was October 4, 2016, where it announced Google Home, Google Wifi, a 4K Chromecast, the Daydream VR headset, and the pair of phones we're looking at today: the Google Pixel and Google Pixel XL. The arrival of the Pixel phones marks the apparent death of the Nexus line; Google says that it has "no plans" for future Nexus devices. With the new branding comes a change in strategy, too. The Pixel brand is about making devices that are 100 percent Google, so despite Google's position as the developer of Android, get ready for Google-designed hardware combined with exclusive Google software.
  • Hands-on with the LeEco Le Pro3: services first, Android second
    LeEco’s flagship Le Pro3 smartphone isn’t trying to compete with the Google Pixel, which puts modern Google services in front of a stock Android backdrop. After playing with the Le Pro3 at the company’s U.S. launch event in San Francisco today, I’m left feeling that it’s an easy, low-cost way to get the full experience of LeEco’s applications. There are proprietary LeEco utility tools like the browser, email, calendar, messages, notes, and phone apps, along with bloatware like Yahoo Weather, but mostly the Pro3 is a means of distribution for the LeEco apps, like Live, LeVidi, and Le. There is also a standard-issue My LeEco app for managing services like EcoPass membership. Under it all is the EUI custom user interface. If you swipe left from the home screen, you see videos that LeEco recommends you watch — not Google Now.
  • Report: Google reaches agreement with CBS for 'Unplugged' web TV service - Fox and Disney may follow