Re: [Mesa-dev] [PATCH v3 07/18] anv/allocator: Add a BO cache

2017-04-04 Thread Chad Versace
On Mon 03 Apr 2017, Jason Ekstrand wrote: > On Mon, Apr 3, 2017 at 3:45 PM, Chad Versace wrote: > > On Mon 03 Apr 2017, Jason Ekstrand wrote: > > > On Mon, Apr 3, 2017 at 12:31 PM, Chad Versace > > > wrote: > > > > Since each VkDevice has a unique drm device fd, and since the kernel > > > > allo

Re: [Mesa-dev] [PATCH v3 07/18] anv/allocator: Add a BO cache

2017-04-04 Thread Chad Versace
On Mon 03 Apr 2017, Jason Ekstrand wrote: > On Mon, Apr 3, 2017 at 5:19 PM, Chad Versace > wrote: > > > On Wed 15 Mar 2017, Jason Ekstrand wrote: > > > This cache allows us to easily ensure that we have a unique anv_bo for > > > each gem handle. We'll need this in order to support multiple-impor

Re: [Mesa-dev] [PATCH v3 07/18] anv/allocator: Add a BO cache

2017-04-03 Thread Jason Ekstrand
On Mon, Apr 3, 2017 at 5:19 PM, Chad Versace wrote: > On Wed 15 Mar 2017, Jason Ekstrand wrote: > > This cache allows us to easily ensure that we have a unique anv_bo for > > each gem handle. We'll need this in order to support multiple-import of > > memory objects and semaphores. > > > > v2 (Ja

Re: [Mesa-dev] [PATCH v3 07/18] anv/allocator: Add a BO cache

2017-04-03 Thread Chad Versace
On Wed 15 Mar 2017, Jason Ekstrand wrote: > This cache allows us to easily ensure that we have a unique anv_bo for > each gem handle. We'll need this in order to support multiple-import of > memory objects and semaphores. > > v2 (Jason Ekstrand): > - Reject BO imports if the size doesn't match t

Re: [Mesa-dev] [PATCH v3 07/18] anv/allocator: Add a BO cache

2017-04-03 Thread Jason Ekstrand
On Mon, Apr 3, 2017 at 4:26 PM, Chad Versace wrote: > On Wed 15 Mar 2017, Jason Ekstrand wrote: > > This cache allows us to easily ensure that we have a unique anv_bo for > > each gem handle. We'll need this in order to support multiple-import of > > memory objects and semaphores. > > > > v2 (Ja

Re: [Mesa-dev] [PATCH v3 07/18] anv/allocator: Add a BO cache

2017-04-03 Thread Chad Versace
On Wed 15 Mar 2017, Jason Ekstrand wrote: > This cache allows us to easily ensure that we have a unique anv_bo for > each gem handle. We'll need this in order to support multiple-import of > memory objects and semaphores. > > v2 (Jason Ekstrand): > - Reject BO imports if the size doesn't match t

Re: [Mesa-dev] [PATCH v3 07/18] anv/allocator: Add a BO cache

2017-04-03 Thread Jason Ekstrand
On Mon, Apr 3, 2017 at 3:45 PM, Chad Versace wrote: > On Mon 03 Apr 2017, Jason Ekstrand wrote: > > On Mon, Apr 3, 2017 at 12:31 PM, Chad Versace > > wrote: > > > > > On Fri 31 Mar 2017, Chad Versace wrote: > > > > On Wed 15 Mar 2017, Jason Ekstrand wrote: > > > > > This cache allows us to easil

Re: [Mesa-dev] [PATCH v3 07/18] anv/allocator: Add a BO cache

2017-04-03 Thread Chad Versace
On Mon 03 Apr 2017, Jason Ekstrand wrote: > On Mon, Apr 3, 2017 at 12:31 PM, Chad Versace > wrote: > > > On Fri 31 Mar 2017, Chad Versace wrote: > > > On Wed 15 Mar 2017, Jason Ekstrand wrote: > > > > This cache allows us to easily ensure that we have a unique anv_bo for > > > > each gem handle.

Re: [Mesa-dev] [PATCH v3 07/18] anv/allocator: Add a BO cache

2017-04-03 Thread Jason Ekstrand
On Mon, Apr 3, 2017 at 12:31 PM, Chad Versace wrote: > On Fri 31 Mar 2017, Chad Versace wrote: > > On Wed 15 Mar 2017, Jason Ekstrand wrote: > > > This cache allows us to easily ensure that we have a unique anv_bo for > > > each gem handle. We'll need this in order to support multiple-import > o

Re: [Mesa-dev] [PATCH v3 07/18] anv/allocator: Add a BO cache

2017-04-03 Thread Chad Versace
On Fri 31 Mar 2017, Chad Versace wrote: > On Wed 15 Mar 2017, Jason Ekstrand wrote: > > This cache allows us to easily ensure that we have a unique anv_bo for > > each gem handle. We'll need this in order to support multiple-import of > > memory objects and semaphores. > > > > v2 (Jason Ekstrand)

Re: [Mesa-dev] [PATCH v3 07/18] anv/allocator: Add a BO cache

2017-03-31 Thread Chad Versace
On Wed 15 Mar 2017, Jason Ekstrand wrote: > This cache allows us to easily ensure that we have a unique anv_bo for > each gem handle. We'll need this in order to support multiple-import of > memory objects and semaphores. > > v2 (Jason Ekstrand): > - Reject BO imports if the size doesn't match t

Re: [Mesa-dev] [PATCH v3 07/18] anv/allocator: Add a BO cache

2017-03-30 Thread Chad Versace
On Wed 15 Mar 2017, Jason Ekstrand wrote: > This cache allows us to easily ensure that we have a unique anv_bo for > each gem handle. We'll need this in order to support multiple-import of > memory objects and semaphores. > > v2 (Jason Ekstrand): > - Reject BO imports if the size doesn't match t

[Mesa-dev] [PATCH v3 07/18] anv/allocator: Add a BO cache

2017-03-15 Thread Jason Ekstrand
This cache allows us to easily ensure that we have a unique anv_bo for each gem handle. We'll need this in order to support multiple-import of memory objects and semaphores. v2 (Jason Ekstrand): - Reject BO imports if the size doesn't match the prime fd size as reported by lseek(). v3 (Jason