[Mesa-dev] [PATCH] anv: change BLOCK_POOL_MEMFD_SIZE to exactly 2GB

Tapani Pälli tapani.palli at intel.com
Fri Mar 10 05:33:28 UTC 2017



On 03/09/2017 10:06 PM, Jason Ekstrand wrote:
> On Thu, Mar 9, 2017 at 8:37 AM, Eero Tamminen <eero.t.tamminen at intel.com
> <mailto:eero.t.tamminen at intel.com>> wrote:
>
>     HI,
>
>     On 09.03.2017 13:28, Tapani Pälli wrote:
>     ...
>
>         We had some discussion today with Eero and came to conclusion
>         that maybe
>         that 2GB is actually too big for 32bit system anyway and should
>         consider
>         to have even smaller block pool size in this case? Or should I
>         just send
>         a patch that adds '- 1' to ftruncate call? Opinions?
>
>
>     Vulkan driver taking 2GB out of application address space, doesn't
>     leave that much for rest of the memory mappings, if the application
>     itself would want to mmap() some large data files.
>
>
> That's not really what's going on.  We ftruncate the file to 2GB to make
> sure it's "big enough" but we only mmap a very small portion of it.
> Dropping the size to 1GB should be just fine.

Right, it's not mapped as whole but pieces of it when utilized. I'll see 
what would be the minimal change here, probably just changing the define 
again, will test with 1GB.

// Tapani


More information about the mesa-dev mailing list