[PATCH 01/10] wined3d: Introduce struct wined3d_dirty_regions.

Matteo Bruni matteo.mystral at gmail.com
Tue Apr 18 11:25:05 CDT 2017

> Why not an array? Stefan already mentioned wined3d_buffer.maps, in a fashion.

Right, an array is probably just better.

>   - Does it really make sense to track regions on the level of struct
> wined3d_resource instead of e.g. strut wined3d_texture? If it does,
> that would make wined3d_buffer.maps redundant.

A unified structure to track both buffer and texture updates would be
nice, if that works out okay in practice.

Either way, I just realized that something like this can be
potentially used to accelerate (partial) texture updates with CSMT,
similarly to e.g. buffers updates in Stefan's patchset. In general it
makes texture uploads resemble buffers, which seems like a good thing.

I think that's no surprise to you. Any plan to explore this idea through?

More information about the wine-devel mailing list