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:
<snip>
+/**
+ * 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 represented by &drm_gpuva objects. It also keeps
track of the
+ * mapping's backing &drm_gem_object buffers.
+ *
+ * &drm_gem_object buffers maintain a list (and a corresponding
list lock) of
+ * &drm_gpuva objects representing all existent GPU VA mappings
using this
+ * &drm_gem_object as backing buffer.
+ *
+ * If the &DRM_GPUVA_MANAGER_REGIONS feature is enabled, a GPU VA
mapping can
+ * only be created within a previously allocated
&drm_gpuva_region, which
+ * represents a reserved portion of the GPU VA space. GPU VA
mappings are not
+ * allowed to span over a &drm_gpuva_region's boundary.
+ *
+ * GPU VA regions can also be flagged as sparse, which allows
drivers to create
+ * sparse mappings for a whole GPU VA region in order to support
Vulkan
+ * 'Sparse Resources'.
Well since we have now found that there is absolutely no technical
reason for having those regions could we please drop them?
I disagree this was the outcome of our previous discussion.
In nouveau I still need them to track the separate sparse page
tables and, as you confirmed previously, Nvidia cards are not the
only cards supporting this feature.
The second reason is that with regions we can avoid merging between
buffers, which saves some effort. However, I agree that this
argument by itself probably doesn't hold too much, since you've
pointed out in a previous mail that:
<cite>
1) If we merge and decide to only do that inside certain boundaries
then those boundaries needs to be provided and checked against. This
burns quite some CPU cycles
2) If we just merge what we can we might have extra page table
updates which cost time and could result in undesired side effects.
3) If we don't merge at all we have additional housekeeping for the
mappings and maybe hw restrictions.
</cite>
However, if a driver uses regions to track its separate sparse page
tables anyway it gets 1) for free, which is a nice synergy.
I totally agree that regions aren't for everyone though. Hence, I
made them an optional feature and by default regions are disabled.
In order to use them drm_gpuva_manager_init() must be called with
the DRM_GPUVA_MANAGER_REGIONS feature flag.
I really would not want to open code regions or have two GPUVA
manager instances in nouveau to track sparse page tables. That would
be really messy, hence I hope we can agree on this to be an optional
feature.
I absolutely don't think that this is a good idea then. This separate
handling of sparse page tables is completely Nouveau specific.
Actually, I rely on what you said in a previous mail when I say it's,
potentially, not specific to nouveau.
<cite>
This sounds similar to what AMD hw used to have up until gfx8 (I
think), basically sparse resources where defined through a separate
mechanism to the address resolution of the page tables. I won't rule
out that other hardware has similar approaches.
</cite>
Ok, sounds like I didn't made my point here clear: AMD does have that
same mechanism for older hw you try to implement here for Nouveau, but
we have *abandoned* it because it is to much trouble and especially
overhead to support! In other words we have said "Ok we would need two
separate components to cleanly handle that, one for newer hw and one for
older hw.".
My point was more about the potential existence of other hardware having
similar concepts.
I, personally, can't judge whether actually making use of having
separate sparse page tables (or similar concepts) makes sense for other
drivers or not. I think it depends on how the hardware works, which
limitations it has in handling page tables, etc.
I definitely recognize your experience and that for AMD you decided its
not worth using a similar mechanism. I would definitely be interested in
the details. Do you mind sharing them?
However, I think we need to differentiate between whether for AMD
hardware you just found an approach that worked out better for your
specific hardware or whether something is fundamentally broken with
separate sparse page tables (or similar concepts) in general.
Do you think there is something fundamentally broken with such an
approach? And if so, why?
What you now try to do is to write one component which works for both.
We have already exercised this idea and came to the conclusion that it's
not a good path to go down. So you're basically just repeating our mistake.
I mean if it's just for Nouveau then I would say feel free to do
whatever you want, but since this component is supposed to be used by
more drivers then I strongly think we need to tackle this from a
different side.
Even when it's optional feature mixing this into the common handling
is exactly what I pointed out as not properly separating between
hardware specific and hardware agnostic functionality.
Optionally having regions is *not* a hardware specific concept,
drivers might use it for a hardware specific purpose though. Which
potentially is is the case for almost every DRM helper.
Drivers can use regions only for the sake of not merging between
buffer boundaries as well. Some drivers might prefer this over "never
merge" or "always merge", depending on the cost of re-organizing page
tables for unnecessary splits/merges, without having the need of
tracking separate sparse page tables.
Its just that I think *if* a driver needs to track separate sparse
page tables anyways its a nice synergy since then there is no extra
cost for getting this optimization.
Well exactly that's the point: I really don't believe that this comes
without extra costs.
If you already have to store some information for purpose A and an
optional purpose B requires the exact same information you would get B
for free.
Which other costs would you see here?
What we could maybe do is to have an two separate functions, one for
updating the data structures and one for merging. When you now call the
merging function with a limit you don't get mappings merged over that
limit and if you don't call the merging function at all you don't get
merges.
Having a separate merging function would work. However, I am against an
interface that takes limit parameters. Having such an interface signals
general compliance with tracking regions to drivers, but without the
offer to do this job in a generic way.
This sounds like a bad compromise to me. I think we should either accept
that some drivers might have a purpose of tracking regions and hence
*optionally* support them or have clear evidence that tracking regions
never ever make sense at all regardless of how a specific hardware
handles it's page tables.
Allowing drivers to set the merge strategy, however, is a good idea. I
could also just add corresponding feature flags to let the driver pick.
But we should have definitely not have the tracking of the ranges inside
the common component. This is something separated.
This is exactly the problem we ran into with TTM as well and I've
spend a massive amount of time to clean that up again. >
Admittedly, I don't know what problems you are referring to. However,
I don't see which kind of trouble it could cause by allowing drivers
to track regions optionally.
Take a look at my 2020 presentation about TTM on FOSDEM.
Regards,
Christian.
Regards,
Christian.
I don't really see a need for them any more.
Regards,
Christian.
