search for: vkbuffer

...anager needs to take >>> regions into account when dealing with mappings to make sure the >>> GPUVA manager doesn't propose drivers to merge over region >>> boundaries. Speaking from userspace PoV, the kernel wouldn't merge >>> mappings from different VKBuffer objects even if they're virtually >>> and physically contiguous. >> >> That are two completely different things and shouldn't be handled in >> a single component. > > They are different things, but they're related in a way that for > handling the m...

...egions into account when dealing with mappings to make sure >>>>>> the GPUVA manager doesn't propose drivers to merge over region >>>>>> boundaries. Speaking from userspace PoV, the kernel wouldn't >>>>>> merge mappings from different VKBuffer objects even if they're >>>>>> virtually and physically contiguous. >>>>> >>>>> That are two completely different things and shouldn't be handled >>>>> in a single component. >>>> >>>> They are differen...

...take >>>> regions into account when dealing with mappings to make sure the >>>> GPUVA manager doesn't propose drivers to merge over region >>>> boundaries. Speaking from userspace PoV, the kernel wouldn't merge >>>> mappings from different VKBuffer objects even if they're virtually >>>> and physically contiguous. >>> >>> That are two completely different things and shouldn't be handled in >>> a single component. >> >> They are different things, but they're related in a way that...

...take > >>> regions into account when dealing with mappings to make sure the > >>> GPUVA manager doesn't propose drivers to merge over region > >>> boundaries. Speaking from userspace PoV, the kernel wouldn't merge > >>> mappings from different VKBuffer objects even if they're virtually > >>> and physically contiguous. > >> > >> That are two completely different things and shouldn't be handled in > >> a single component. > > > > They are different things, but they're related in a way t...

...ve no concept of this in Xe, >> e.g. we can create a VM and the entire address space is managed exactly >> the same. > > The idea for alloc/free is to let UMDs allocate a portion of the VA > space (which I call a region), basically the same thing Vulkan > represents with a VKBuffer. If that's mangled into the same component/interface then I can say from experience that this is a pretty bad idea. We have tried something similar with radeon and it turned out horrible. What you want is one component for tracking the VA allocations (drm_mm based) and a different componen...

...need this operation? We have no concept of this in Xe, > e.g. we can create a VM and the entire address space is managed exactly > the same. The idea for alloc/free is to let UMDs allocate a portion of the VA space (which I call a region), basically the same thing Vulkan represents with a VKBuffer. It serves two purposes: 1. It gives the kernel (in particular the GPUVA manager) the bounds in which it is allowed to merge mappings. E.g. when a user request asks for a new mapping and we detect we could merge this mapping with an existing one (used in another VKBuffer than the mapping reque...