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

Radeon VRAM Optimizations Coming, But Help Is Needed

AMD

Published on 11 January 2014 05:00 PM EST
Written by Lauri Kasanen in AMD
129 Comments

Got a workload that runs badly on the r600g Radeon Gallium3D driver? You can help fix it! Optimizations are coming to the open-source Radeon Linux driver for video memory usage.

I'm currently working on my thesis (Software Engineering), studying the VRAM behavior of radeon. For r600g, much of the remaining gap to fglrx can be explained by less than optimal VRAM use. There's fragmentation, and there's ping-pong of buffers to and from VRAM.

You can help by recording a trace of the app's memory use. If you use Oibaf's PPA, you're set; if you build Mesa yourself, please apply the patches from the stats6 branch.

Run the app with the R600_DEBUG environment variable set to enable tracing (bostats), for example "R600_DEBUG=bostats dota2". The trace will be written to /tmp/bostats.[pid].dota2.

Once a few minutes of gameplay have been captured, exit the game. Please compress this file with XZ, upload somewhere (dropbox, anonfiles, bayfiles, etc) and e-mail me the link to cand at gmx dot com.

Please include a description of the app, settings used, and the version of the app. If it's a private application, please specify that too.

I would really appreciate traces from commercial apps, both native and those used via Wine. I can record most open-source apps myself, but if you have a specific case (for example, Xonotic with specific settings only) that runs badly, please record that.

Notes:

- The machine doesn't have to be the slow one. For example, if WoW is slow on your integrated card, but fast on a discrete, feel free to record on the discrete. The trace will be the same, assuming settings are the same.
- There is nothing confidential in the trace, so any private apps are safe to record.
- If your /tmp is in RAM, a big trace might fill it -- use TMPDIR=/home/foo etc to specify a dir on storage.
- While radeonsi could be used in theory, it has not been tested, and traces from it are incorrect (they lack much of the cpu statistics).

Thanks to Lauri Kasanen for reaching out to us so that Phoronix readers can help him in having a successful thesis and his continued work on improving the open-source Radeon Linux graphics driver. For any questions, please drop by the forums.

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