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 Benchmarking Platform
Phoromatic Test Orchestration

Google Pushes More Mesa / Gallium3D Patches

Mesa

Published on 16 June 2013 04:51 PM EDT
Written by Michael Larabel in Mesa
8 Comments

More Mesa / Gallium3D patches out of Google have come about this month for improving the open-source graphics stack.

Google has been using Mesa/Gallium3D drivers for use on their Intel-powered Chromebooks. Google had invested heavily in the Intel Gallium3D driver for use on their older Chromebooks, but now they are starting to push more of their Mesa/Gallium3D changes that have been building up in months past.

Published today on the mailing list by Google's Frank Henigman is an LLVM compiler cache for Gallium3D. "This works (has been in Chrome OS for a while) but only for vertex shaders, not geometry shaders nor llvmpipe...I don't know how much other apps care but it's a big win for Chrome because just opening an empty tab recompiles some shaders and takes hundreds of milliseconds on a low-end chromebook. Revisiting a page with a bunch of shaders is seconds faster....My cache comes in before generating LLVM source however, thus should have bigger savings than can be realized at the LLVM level."

Frank also posted per-texture locking support. This work allows uploading textures from one thread concurrently with drawing in another thread, thus a performance benefit.

Another set of patches out of Google recently allows saving about 1MB per texture with LLVM vertex shaders. This memory-saving work has been in Google's patched Mesa version for a while and is now being submitted for possible upstream inclusion.

Overall, it's good to see Google's continued Mesa involvement and furthering the open-source Linux graphics drivers for Chrome OS.

About The Author
Michael Larabel is the principal author of Phoronix.com and founded the web-site in 2004 with a focus on enriching the Linux hardware experience and being the largest web-site devoted to Linux hardware reviews, particularly for products relevant to Linux gamers and enthusiasts but also commonly reviewing servers/workstations and embedded Linux devices. Michael has written more than 10,000 articles covering the state of Linux hardware support, Linux performance, graphics hardware drivers, and other topics. Michael is also the lead developer of the Phoronix Test Suite, Phoromatic, and OpenBenchmarking.org automated testing software. He can be followed via and or contacted via .
Latest Articles & Reviews
  1. Sub-$20 802.11n USB WiFi Adapter That's Linux Friendly
  2. The Lenovo T450s Is Working Beautifully With Linux
  3. Linux 4.0 SSD EXT4 / Btrfs / XFS / F2FS Benchmarks
  4. Linux 4.0 Hard Drive Comparison With Six File-Systems
  5. Lenovo ThinkPad T450s Broadwell Preview
  6. How Open-Source Allowed Valve To Implement VULKAN Much Faster On The Source 2 Engine
Latest Linux News
  1. Linux-Powered Endless Computer Raises $100k+ In A Few Days
  2. GCC 5.1 RC2 Arrives, GCC 5.1 Planned For Next Week
  3. F2FS For Linux 4.1 Has New Features & Fixes
  4. Phoronix Server Upgrade This Weekend: Dual Haswell Xeons, 96GB DDR4
  5. Google's Experimental QUIC Transport Protocol Is Showing Promise
  6. Red Hat Joins Khronos, The Group Behind OpenGL & Vulkan
  7. NetworkManager Drops WiMAX Support
  8. Wine 1.7.41 Works More On Kernel Job Objects, MSI Patches
  9. Linux 4.1 Has Improvements For The Multi-Queue Block Layer
  10. X.Org Looks To Have Six Summer Projects
Most Viewed News This Week
  1. Nouveau: NVIDIA's New Hardware Is "VERY Open-Source Unfriendly"
  2. Linux 4.0 Kernel Released
  3. Microsoft Announces An LLVM-Based Compiler For .NET
  4. Linux 4.1 Brings Many Potentially Risky x86/ASM Changes
  5. Encryption Support For EXT4
  6. VirtualBox 5.0 Beta 2 Released
  7. Mozilla Start Drafting Plans To Deprecate Insecure HTTP
  8. KDBUS Is Taking A Lot Of Heat, Might Be Delayed From Mainline Linux Kernel