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

There's Hope For DMA-BUF With Non-GPL Drivers

NVIDIA

Published on 20 February 2012 07:16 AM EST
Written by Michael Larabel in NVIDIA
43 Comments

There's some resurrected hope for the kernel symbols of the DMA-BUF buffer sharing mechanism to be not restricted to only GPL drivers, which started off as a request by NVIDIA. This could lead to better NVIDIA Optimus support under Linux, among other benefits.

DMA-BUF is the buffer sharing mechanism for the Linux kernel that was introduced in the 3.3 cycle for zero-copy sharing of buffers between kernel drivers. This work originally came out of the Linaro project since there's a need for such a mechanism by various ARM SoC driver developers. However, there's also benefits to this work when it comes to GPU hot-plugging, OpenCL / GPGPU computing, and multi-GPU configurations like NVIDIA Optimus.

To learn more about DMA-BUF for Linux, watch this DMA-BUF video from FOSDEM 2012 when Daniel Vetter of Intel was speaking about this infrastructure.

Back in January there was a request by NVIDIA that the DMA-BUF kernel symbols be not exported GPL-only, which would prevent them from taking advantage of this buffer sharing mechanism in their proprietary driver. This would inhibit them from being able to easily/cleanly share buffers between their binary driver and say the Intel open-source driver in Optimus cases where there's both Intel and NVIDIA graphics. Or for buffer-sharing between an open-source NVIDIA Tegra kernel driver and the binary driver with a GeForce GPU, a case that one of the requesting NVIDIA engineer mentioned.

The upstream open-source Linux kernel developers weren't really in favor of this change to allow non-GPL drivers access to DMA-BUF. However, one of the developers involved with DMA-BUF, Rob Clark of Texas Instruments, has more positive news to now share. Below is the message he posted to the kernel mailing list on Sunday concerning this DMA-BUF licensing.
We discussed this topic at the kernel-gfx mini-summit at ELC. Following the discussion, I agree that dma-buf infrastructure is intended as an interface between driver subsystems. And because (for now) all the other arm SoC gl(es) stacks unfortunately involve a closed src userspace, and since I consider userspace and kernel as tightly coupled in the realm of graphics stacks, I don't think we can really claim the moral high-ground here. So I can't object to use of EXPORT_SYMBOL() instead of EXPORT_SYMBOL_GPL().

That said, I expect the dma-buf infrastructure to still be evolving and it is the responsibility for out-of-tree users of the API (GPL or otherwise) to adapt as the dma-buf API changes. And there isn't much the in-tree drivers can do when it comes to debugging of buffer sharing issues with out-of-tree drivers (binary or otherwise), leaving the debugging responsibility to the owners of different out-of-tree drivers.

BR,
-R

This would be marked as a win for NVIDIA (and potentially AMD, among others) as well as Linux desktop users just looking for the best supported hardware experience, assuming this export symbol change goes through.

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. Ubuntu 15.04 Is The Easy Path To Better Performance On Intel Broadwell
  2. NVIDIA's Latest Maxwell Line-Up Against AMD With Catalyst On Linux
  3. Preliminary Tests Of Intel Sandy Bridge & Ivy Bridge vs. Broadwell
  4. AMD FX-8320E Performance On Linux
  5. Linux Compiler Benchmarks Of LLVM Clang 3.5 vs. LLVM Clang 3.6-rc1
  6. Intel Broadwell HD Graphics 5500: Windows 8.1 vs. Linux
Latest Linux News
  1. Atomic Mode-Setting/Display Support Progresses In Linux 3.20
  2. NVIDIA 340.76 Brings Three Stable Fixes
  3. Intel Broadwell-U P-State vs. ACPI CPUFreq Scaling Linux Performance
  4. DragonFlyBSD Is Almost To Linux 3.10 Era Intel Graphics Support
  5. New Beta Of Witcher 2 Aims For Greater Performance
  6. NVIDIA Tegra DRM Driver Supports Atomic Mode-Setting In Linux 3.20
  7. Linux "GHOST" Vulnerability Hits Glibc Systems
  8. Linux Game Publishing Remains Offline, Three Years After The CEO Shakeup
  9. PlayStation 4 System Compiler Support Landing In LLVM
  10. Now-Closed KDE Vulnerabilities Remind Us X11 Screen Locks / Screensavers Are Insecure
Most Viewed News This Week
  1. Windows 10 To Be A Free Upgrade: What Linux Users Need To Know
  2. LibreOffice 4.4 Is Coming Soon With New Features
  3. TraceFS: The Newest Linux File-System
  4. My Initial Intel Broadwell Linux Experience With The ThinkPad X1 Carbon
  5. Broadwell Linux Ultrabook Running MUCH Cooler Than Haswell
  6. LZHAM 1.0 Lossless Data Compression Codec Released
  7. Interstellar Marines On Linux With Catalyst: Bull S*#@
  8. Linux Users Upset By Chromium's Busted HiDPI Support