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

Concerns Come Over Linaro's Memory Manager Plans

Hardware

Published on 21 April 2011 07:52 AM EDT
Written by Michael Larabel in Hardware
2 Comments

On Monday there was the Phoronix news item about Linaro aiming to unify Linux memory management; in particular it's for embedded ARM platforms and making the existing Linux video memory managers more compatible with that of the SoC designs and drivers. They want the memory manager to be able to share memory buffers across different devices and processes, which is something somewhat sought after already by Linux graphics developers for GEM/TTM, but this may end up leading to a new memory management fork.

On Monday, the Linaro group brought up the issue on the DRI development list, among other lists, but it didn't spark any noteworthy exchanges. Yesterday though it was brought up on the Wayland Display Server mailing list where a vocal discussion ensued. It's this thread.

Tiago Vignatti began by asking whether any of Linaro's kernel memory management work would be pushed upstream or whether this is a fork of the community. Linaro though plans to push the work back upstream into the mainline kernel tree.

Others also chimed in. E.g. "Not again, due! Does DRI has some mentally wrong that cann't be fixed other than re-create? Forking is not always the best thing. A is suck, I can write batter one that does exactly the same as A, but more clean code. So I go ahead and write new B. Because B is new, so I have to fix fix fix fix bugs. Long time after, B fixed all bugs and function the same as A, and, the code is now as buggy as A's."

Tom Cooksey mentions that since GEM/TTM don't current allow sharing of buffers between drivers and don't allow physically contiguous memory allocations, Linaro may end up with "a good chance TTM will be ripped out, stuck into its own driver (with its own device node /dev/ttm) and extended to meet everyone's requirements."

But, for example, upstream TTM actually wants the support for sharing of buffers between drivers since it would be needed for some multi-card configurations, etc. TTM reworking is also needed for being able to handle OpenCL on its stack, etc.

The PathScale engineers and their hired hands had also forked the PSCNV driver for the memory management reasons, among others, to adapt it to better handle such work. PathScale's prinicipal concerns boiled down to no memory security/protection, under TTM's current model the buffer objects can be moved at any time, and TTM being hard to port to other operating systems.

Linaro's Jesse Barker had the following to say on the matter: "No one wants to reinvent the wheel unless it's absolutely necessary (and it typically isn't), but SoC vendors and software partners are encountering problems that they haven't been able to solve with the current upstream mechanisms. Initially, we're primarily concerned with making sure we're asking the right questions and identifying the right people to ask and answer them. Everything will be done publicly and in the mainline. No forking, no revolution, just problem solving. If it turns out that someone else has beaten us to it, that's great."

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 Linux Hardware Reviews
  1. Even With Re-Clocking, Nouveau Remains Behind NVIDIA's Proprietary Linux Driver
  2. The Power Consumption & Efficiency Of Open-Source GPU Drivers
  3. AMD R600g/RadeonSI Performance On Linux 3.16 With Mesa 10.3-devel
  4. Intel Pentium G3258 On Linux
Latest Linux Articles
  1. Updated Source Engine Benchmarks On The Latest AMD/NVIDIA Linux Drivers
  2. Nouveau vs. Radeon vs. Intel Tests On Linux 3.16, Mesa 10.3-devel
  3. KVM Benchmarks On Ubuntu 14.10
  4. X.Org Server 1.16 Officially Released With Terrific Features
Latest Linux News
  1. GNOME/GTK On Wayland Gains Focus At GUADEC
  2. GNOME Stakeholders Take Issue With Groupon Over their Gnome
  3. GStreamer VA-API Plug-In Update Adds New Features
  4. Qt 5.4 Going Into Feature Freeze Next Week With Exciting Changes
  5. OpenSUSE Factory Turns Into Rolling Release Distribution
  6. "The World's Most Highly-Assured OS" Kernel Open-Sourced
  7. NVIDIA Is Working Towards VDPAU H.265/HEVC Support
  8. Hawaii Bug-Fixes Start Hitting Mainline RadeonSI Gallium3D
  9. The FFmpeg vs. Libav War Continues In Debian Land
  10. Grand Theft Auto Running On Direct3D Natively On Linux Shows Gallium3D Potential
Latest Forum Discussions
  1. Grand Theft Auto Running On Direct3D Natively On Linux Shows Gallium3D Potential
  2. AMD Athlon 5350 APU On Linux
  3. Linus Torvalds On GCC 4.9: Pure & Utter Crap
  4. Updated and Optimized Ubuntu Free Graphics Drivers
  5. Debian + radeonsi
  6. Open-source drivers on ATI R7 260X
  7. List of Linux friendly Kickstarter projects
  8. Porting Mesa to the Playstation 2