Hi, On Fri, Jun 28, 2024 at 01:29:17PM GMT, Thierry Reding wrote: > On Tue, May 21, 2024 at 02:06:19PM GMT, Daniel Vetter wrote: > > On Thu, May 16, 2024 at 09:51:35AM -0700, John Stultz wrote: > > > On Thu, May 16, 2024 at 3:56 AM Daniel Vetter <daniel@xxxxxxxx> wrote: > > > > On Wed, May 15, 2024 at 11:42:58AM -0700, John Stultz wrote: > > > > > But it makes me a little nervous to add a new generic allocation flag > > > > > for a feature most hardware doesn't support (yet, at least). So it's > > > > > hard to weigh how common the actual usage will be across all the > > > > > heaps. > > > > > > > > > > I apologize as my worry is mostly born out of seeing vendors really > > > > > push opaque feature flags in their old ion heaps, so in providing a > > > > > flags argument, it was mostly intended as an escape hatch for > > > > > obviously common attributes. So having the first be something that > > > > > seems reasonable, but isn't actually that common makes me fret some. > > > > > > > > > > So again, not an objection, just something for folks to stew on to > > > > > make sure this is really the right approach. > > > > > > > > Another good reason to go with full heap names instead of opaque flags on > > > > existing heaps is that with the former we can use symlinks in sysfs to > > > > specify heaps, with the latter we need a new idea. We haven't yet gotten > > > > around to implement this anywhere, but it's been in the dma-buf/heap todo > > > > since forever, and I like it as a design approach. So would be a good idea > > > > to not toss it. With that display would have symlinks to cma-ecc and cma, > > > > and rendering maybe cma-ecc, shmem, cma heaps (in priority order) for a > > > > SoC where the display needs contig memory for scanout. > > > > > > So indeed that is a good point to keep in mind, but I also think it > > > might re-inforce the choice of having ECC as a flag here. > > > > > > Since my understanding of the sysfs symlinks to heaps idea is about > > > being able to figure out a common heap from a collection of devices, > > > it's really about the ability for the driver to access the type of > > > memory. If ECC is just an attribute of the type of memory (as in this > > > patch series), it being on or off won't necessarily affect > > > compatibility of the buffer with the device. Similarly "uncached" > > > seems more of an attribute of memory type and not a type itself. > > > Hardware that can access non-contiguous "system" buffers can access > > > uncached system buffers. > > > > Yeah, but in graphics there's a wide band where "shit performance" is > > defacto "not useable (as intended at least)". > > > > So if we limit the symlink idea to just making sure zero-copy access is > > possible, then we might not actually solve the real world problem we need > > to solve. And so the symlinks become somewhat useless, and we need to > > somewhere encode which flags you need to use with each symlink. > > > > But I also see the argument that there's a bit a combinatorial explosion > > possible. So I guess the question is where we want to handle it ... > > Sorry for jumping into this discussion so late. But are we really > concerned about this combinatorial explosion in practice? It may be > theoretically possible to create any combination of these, but do we > expect more than a couple of heaps to exist in any given system? I don't worry too much about the number of heaps available in a given system, it would indeed be fairly low. My concern is about the semantics combinatorial explosion. So far, the name has carried what semantics we were supposed to get from the buffer we allocate from that heap. The more variations and concepts we'll have, the more heap names we'll need, and with confusing names since we wouldn't be able to change the names of the heaps we already have. > Would it perhaps make more sense to let a platform override the heap > name to make it more easily identifiable? Maybe this is a naive > assumption, but aren't userspace applications and drivers not primarily > interested in the "type" of heap rather than whatever specific flags > have been set for it? I guess it depends on what you call the type of a heap. Where we allocate the memory from, sure, an application won't care about that. How the buffer behaves on the other end is definitely something applications are going to be interested in though. And if we allow any platform to change a given heap name, then a generic application won't be able to support that without some kind of platform-specific configuration. > For example, if an applications wants to use a protected buffer, the > application doesn't (and shouldn't need to) care about whether the heap > for that buffer supports ECC or is backed by CMA. All it really needs to > know is that it's the system's "protected" heap. I mean... "protected" very much means backed by CMA already, it's pretty much the only thing we document, and we call it as such in Kconfig. But yeah, I agree that being backed by CMA is probably not what an application cares about (and we even have might some discussions about that), but if the ECC protection comes at a performance cost then it will very much care about it. Or if it comes with caches enabled or not. > This rather than try to represent every possible combination we > basically make this a "configuration" issue. System designers need to > settle on whatever combination of flags work for all the desired use- > cases and then we expose that combination as a named heap. This just pushes the problem down to applications, and carry the flags mentioned earlier in the heap name. So the same information, but harder to process or discover for an application. > One problem that this doesn't solve is that we still don't have a way of > retrieving these flags in drivers which may need them. I'm not sure drivers should actually need to allocate from heaps, but we could do it just like I suggested we'd do it for applications: we add a new function that allows to discover what a given heap capabilities are. And then we just have to iterate and choose the best suited for our needs. Maxime
Attachment:
signature.asc
Description: PGP signature
