Hi all, On 10 April 2017 at 08:18, Kenneth Graunke <kenn...@whitecape.org> wrote: > From: Daniel Vetter <daniel.vet...@ffwll.ch> > > This was done because the kernel has 1 global address space, shared > with all render clients, for gtt mmap offsets, and that address space > was only 32bit on 32bit kernels. > > This was fixed in > > commit 440fd5283a87345cdd4237bdf45fb01130ea0056 > Author: Thierry Reding <tred...@nvidia.com> > Date: Fri Jan 23 09:05:06 2015 +0100 > > drm/mm: Support 4 GiB and larger ranges > > which shipped in 4.0. Of course you still want to limit the bo cache > to a reasonable size on 32bit apps to avoid ENOMEM, but that's better > solved by tuning the cache a bit. On 64bit, this was never an issue. > While this patch is _not_ a bugfix, it inspired an interesting question/topic:
Do we want to backport fixes from mesa's bufmgr to libdrm_intel? Or in general what's the plan about the library - leave it as-is, sync fixes, remove it, other. Can we have the decision documented somewhere, please? After all: good science/engineering is good documentation. Thanks Emil _______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
