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. AMD Open-Sources "Addrlib" From Catalyst
  2. AMD Releases New "AMDGPU" Linux Kernel Driver & Mesa Support
  3. A Gigabyte Sandy/Ivy Bridge Motherboard Now Handled By Coreboot
  4. Linux 3.16 Through Linux 4.0 Performance Benchmarks
  5. Intel's Windows Driver Now Supports OpenGL 4.4, Linux Driver Still With OpenGL 3.3
  6. DRM Graphics Updates Sent In For The Linux 4.1 Kernel
  7. More eBPF Improvements Heading To Linux 4.1
  8. LLDB Is Getting Into Shape For Linux 64-bit Debugging
  9. Wine-Staging 1.7.41 Works On Improved Debugging Support
  10. GNOME 3.18 Release Schedule: 23 September Release
Most Viewed News This Week
  1. Nouveau: NVIDIA's New Hardware Is "VERY Open-Source Unfriendly"
  2. LibreOffice 4.5 Bumped To Become LibreOffice 5.0
  3. Linux Audio Is Being Further Modernized With The 4.1 Kernel
  4. KDBUS Is Taking A Lot Of Heat, Might Be Delayed From Mainline Linux Kernel
  5. VirtualBox 5.0 Beta 2 Released
  6. ZFS & Libdvdcss Should Soon Be In Debian
  7. Ubuntu 15.04 Now Under Final Freeze
  8. EXT4 In Linux 4.1 Adds File-System Level Encryption