Faith Ekstrand

I'm going to attempt to list a set of atomic capabilities for us to use on Intel that describe everything we care about. Not all of them will apply to...

@cubanismo I must say, calling it a "descriptor set" makes me shudder a bit and think of other similarly named over-complicated solutions to not-that-complicated problems. :-)

I know @robclark made some comments in the direction of (1) but I think I'd prefer (2) if we can make it work. One option would be to provide, with...

I don't think that magically loading things requires that we have a particularly complicated mapping. You get a list of capability/restriction tags from each driver/API in the negotiation. With that...

@robclark, I think the question of where you get the caps plays into this as well (#6). I would ideally like to see you get the caps from your GL...

My preference would be to keep the "get allocation capabilities" portion decentralized so each driver has an entrypoint for it. Why? Because it means that in the common case of...

@lynxeye-dev, Your comment just made me realize that I've been making assumptions about what I mean by "decentralized". I think we have 4 different levels of "centralization": 1. Kernel (yes,...

@robclark First off, I should say that I don't intend liballoc (I guess that's what we're calling it now) to be very thick. For most operations, it will simply look...

Woah... Lots of comments... I'll try to address stuff one-at-a-time. > @jekstrand You're saying you want caps/constraint querying done only through GL/Vulkan/etc., not through the allocation API itself? I don't...

From @cubanismo: Good summary Rob. I personally think where dataformat will shine is in advanced use cases, probably many of which we aren’t seeing or haven’t thought of yet because...