* Danilo Krummrich [230313 19:46]:
> On 3/7/23 23:43, Liam R. Howlett wrote:
> > * Danilo Krummrich [230306 10:46]:
> > > On 3/2/23 03:38, Liam R. Howlett wrote:
> > > > * Danilo Krummrich [230227 08:17]:
> > > >
> > > > ...
> > > > > > > Would this variant be significantly more efficient?
> >
On 3/7/23 23:43, Liam R. Howlett wrote:
* Danilo Krummrich [230306 10:46]:
On 3/2/23 03:38, Liam R. Howlett wrote:
* Danilo Krummrich [230227 08:17]:
...
Would this variant be significantly more efficient?
Well, what you are doing is walking the tree to see if there's anything
there...
* Danilo Krummrich [230306 10:46]:
> On 3/2/23 03:38, Liam R. Howlett wrote:
> > * Danilo Krummrich [230227 08:17]:
> >
> > ...
> > > > > Would this variant be significantly more efficient?
> > > >
> > > > Well, what you are doing is walking the tree to see if there's anything
> > > > there...
On 3/2/23 03:38, Liam R. Howlett wrote:
* Danilo Krummrich [230227 08:17]:
...
Would this variant be significantly more efficient?
Well, what you are doing is walking the tree to see if there's anything
there... then re-walking the tree to store it. So, yes, it's much more
efficient..
On 2/28/23 17:24, Liam R. Howlett wrote:
* Danilo Krummrich [230227 21:17]:
On Tue, Feb 21, 2023 at 01:20:50PM -0500, Liam R. Howlett wrote:
* Danilo Krummrich [230217 08:45]:
Add infrastructure to keep track of GPU virtual address (VA) mappings
with a decicated VA space manager
* Danilo Krummrich [230227 08:17]:
...
> > > Would this variant be significantly more efficient?
> >
> > Well, what you are doing is walking the tree to see if there's anything
> > there... then re-walking the tree to store it. So, yes, it's much more
> > efficient.. However, writing is
* Danilo Krummrich [230227 21:17]:
> On Tue, Feb 21, 2023 at 01:20:50PM -0500, Liam R. Howlett wrote:
> > * Danilo Krummrich [230217 08:45]:
> > > Add infrastructure to keep track of GPU virtual address (VA) mappings
> > > with a decicated VA space manager implementation.
> > >
> > > New UAPIs,
On Tue, Feb 21, 2023 at 01:20:50PM -0500, Liam R. Howlett wrote:
> * Danilo Krummrich [230217 08:45]:
> > Add infrastructure to keep track of GPU virtual address (VA) mappings
> > with a decicated VA space manager implementation.
> >
> > New UAPIs, motivated by Vulkan sparse memory bindings
On 2/23/23 20:09, Liam R. Howlett wrote:
* Danilo Krummrich [230222 13:13]:
On 2/21/23 19:20, Liam R. Howlett wrote:
* Danilo Krummrich [230217 08:45]:
Add infrastructure to keep track of GPU virtual address (VA) mappings
with a decicated VA space manager implementation.
New UAPIs,
* Danilo Krummrich [230222 13:13]:
> On 2/21/23 19:20, Liam R. Howlett wrote:
> > * Danilo Krummrich [230217 08:45]:
> > > Add infrastructure to keep track of GPU virtual address (VA) mappings
> > > with a decicated VA space manager implementation.
> > >
> > > New UAPIs, motivated by Vulkan
On 2/23/23 08:06, Christian König wrote:
Am 22.02.23 um 17:40 schrieb Danilo Krummrich:
On 2/22/23 16:14, Christian König wrote:
Am 22.02.23 um 16:07 schrieb Danilo Krummrich:
On 2/22/23 11:25, Christian König wrote:
Am 17.02.23 um 14:44 schrieb Danilo Krummrich:
+/**
+ * DOC: Overview
Am 22.02.23 um 17:40 schrieb Danilo Krummrich:
On 2/22/23 16:14, Christian König wrote:
Am 22.02.23 um 16:07 schrieb Danilo Krummrich:
On 2/22/23 11:25, Christian König wrote:
Am 17.02.23 um 14:44 schrieb Danilo Krummrich:
+/**
+ * DOC: Overview
+ *
+ * The DRM GPU VA Manager,
On 2/21/23 19:20, Liam R. Howlett wrote:
* Danilo Krummrich [230217 08:45]:
Add infrastructure to keep track of GPU virtual address (VA) mappings
with a decicated VA space manager implementation.
New UAPIs, motivated by Vulkan sparse memory bindings graphics drivers
start implementing, allow
On 2/22/23 16:14, Christian König wrote:
Am 22.02.23 um 16:07 schrieb Danilo Krummrich:
On 2/22/23 11:25, Christian König wrote:
Am 17.02.23 um 14:44 schrieb Danilo Krummrich:
+/**
+ * DOC: Overview
+ *
+ * The DRM GPU VA Manager, represented by struct drm_gpuva_manager
keeps track
+ *
Am 22.02.23 um 16:07 schrieb Danilo Krummrich:
On 2/22/23 11:25, Christian König wrote:
Am 17.02.23 um 14:44 schrieb Danilo Krummrich:
+/**
+ * DOC: Overview
+ *
+ * The DRM GPU VA Manager, represented by struct drm_gpuva_manager
keeps track
+ * of a GPU's virtual address (VA) space and
On 2/22/23 11:25, Christian König wrote:
Am 17.02.23 um 14:44 schrieb Danilo Krummrich:
+/**
+ * DOC: Overview
+ *
+ * The DRM GPU VA Manager, represented by struct drm_gpuva_manager
keeps track
+ * of a GPU's virtual address (VA) space and manages the
corresponding virtual
+ * mappings
Am 17.02.23 um 14:44 schrieb Danilo Krummrich:
Add infrastructure to keep track of GPU virtual address (VA) mappings
with a decicated VA space manager implementation.
New UAPIs, motivated by Vulkan sparse memory bindings graphics drivers
start implementing, allow userspace applications to
* Danilo Krummrich [230217 08:45]:
> Add infrastructure to keep track of GPU virtual address (VA) mappings
> with a decicated VA space manager implementation.
>
> New UAPIs, motivated by Vulkan sparse memory bindings graphics drivers
> start implementing, allow userspace applications to request
: 48075a66fca613477ac1969b576a93ef5db0164f
patch link:
https://lore.kernel.org/r/20230217134422.14116-6-dakr%40redhat.com
patch subject: [PATCH drm-next v2 05/16] drm: manager to keep track of GPUs VA
mappings
config: mips-allyesconfig
(https://download.01.org/0day-ci/archive/20230218/202302180805.b0ab40v5
Add infrastructure to keep track of GPU virtual address (VA) mappings
with a decicated VA space manager implementation.
New UAPIs, motivated by Vulkan sparse memory bindings graphics drivers
start implementing, allow userspace applications to request multiple and
arbitrary GPU VA mappings of
20 matches
Mail list logo