1. Computers
  2. Display Drivers
  3. Graphics Cards
  4. Memory
  5. Motherboards
  6. Processors
  7. Software
  8. Storage
  9. Operating Systems


Facebook RSS Twitter Twitter Google Plus


Phoronix Test Suite

OpenBenchmarking.org

Having SNAppy Intel 2D Acceleration In 2012

Michael Larabel

Published on 31 January 2012
Written by Michael Larabel
Page 1 of 8 - 8 Comments

Here's a new look at Intel's Sandy Bridge New Acceleration (SNA) architecture within their DDX graphics driver. Testing in this article was done across three systems (mobile and desktop class Sandy Bridge hardware as well as an Ironlake system) seeing how well the latest code is performing in an effort to provide a better Intel 2D experience.

Sandy Bridge New Acceleration, which was designed by Chris Wilson at Intel's Open-Source Technology Center to be a crazy fast acceleration architecture and formally introduced in June of 2011, has been making much progress. In fact, nearly all of the activity still going on within the xf86-video-intel DDX driver is SNA-related. There isn't too much fun left to be had within the Intel X.Org driver with most of the interesting work going into the Intel DRM kernel driver (and Mesa for the 3D work).

SNA has turned into Chris Wilson's personal vendetta within the Intel Linux graphics driver. SNA-related commits are still happening almost daily; there's been almost 100 SNA commits in the past week and about 350 SNA commits since the start of 2012. While much activity has been happening around Sandy Bridge New Acceleration, and in most cases it's significantly faster than the stock UXA (a gutted EXA with GEM handling) for 2D acceleration, it's still not the default acceleration architecture. SNA does have accelerated back-ends for older generations of Intel integrated graphics, but occasionally with all of this work happening there are regressions and other issues that come up related to SNA.

As far as whether SNA will ever be the default, when talking about it with Keith Packard at XDC2011 Chicago he made it sound like it was unlikely to make the switch from the stock UXA mode. When asking Chris Wilson about the future of SNA this past weekend and whether it would become the default, he said, "At this moment in time, I have no idea."

Chris went on to say, "I just hope the future where we have a DDX that is never slower or more power hungry than simply using the CPU, ala shadowfb, and is truly competitive with not only our Windows colleagues but with competing chipsets arrives sooner rather than later." It's a nice mission, so let's see how SNA is running today.

<< Previous Page
1
Latest Linux Hardware Reviews
  1. Btrfs On 4 x Intel SSDs In RAID 0/1/5/6/10
  2. AMD Radeon R9 290 On Ubuntu 14.10: RadeonSI Gallium3D vs. Catalyst
  3. MSI X99S SLI PLUS On Linux
  4. NVIDIA GeForce GTX 970 Offers Great Linux Performance
Latest Linux Articles
  1. NVIDIA's Linux Driver Can Deliver Better OpenGL Performance Than Windows 8.1
  2. Windows 8.1 vs. Ubuntu 14.10 With Intel HD Graphics
  3. 6-Way Ubuntu 14.10 Radeon Gallium3D vs. Catalyst Driver Comparison
  4. NVIDIA vs. Nouveau Drivers On Ubuntu 14.10
Latest Linux News
  1. GCC's JIT Compiler Support Moves A Step Closer To Mainline
  2. Freescale's iMX DRM Driver Sees Big Changes
  3. Enlightenment's New Wayland Compositor Code Is Now Functional, Supports XDG-Shell
  4. Don't Use Fedora's Fedup Right Now Due To A Bug With Systemd
  5. AMD On Linux & Systemd Were Very Popular This Month
  6. Wine 1.7.30 Continues Work On DirectWrite & Offers Regedit Fixes
  7. Has The Sky Fallen? Qualcomm Contributes To Freedreno's DRM/KMS Driver
  8. Manjaro Works To Make Calamares A Distribution-Independent Installer
  9. DisplayLink USB 3.0 Support Sounds Like A Mess
  10. PulseAudio Gains A Native Bluetooth Headset Backend
Latest Forum Discussions
  1. Civilization: Beyond Earth Overcoming Linux GPU Driver Problems
  2. How to get rid of Linux
  3. Updated and Optimized Ubuntu Free Graphics Drivers
  4. Step by Step install of Latest Nvidia Driver Article Request
  5. Closed source to opensource
  6. What Would You Like To See Next?
  7. Is foolish currently develop in machine code, hexadecimal and assembly?
  8. Reducing The CPU Usage In Mesa To Improve Performance