riperiperi 7c5ead1c19 Fast path for Inline2Memory buffer write that skips write tracking (#2624) ... * Fast path for Inline2Memory buffer write This PR adds a method to PhysicalMemory that attempts to write all cached resources directly, so that memory tracking can be avoided. The goal of this is both to avoid flushing buffer data, and to avoid raising the sequence number when data is written, which causes buffer and texture handles to be re-checked. This currently only targets buffers, with a side check on textures that falls back to a tracked write if any exist within the target range. It's not expected to write textures from here - this is just a mechanism to protect us if someone does decide to do that. It's possible to add a fast path for this in future (and for ShaderCache, once that starts using tracking) The forced read before inline2memory begins has been skipped, as the data is fully written when the transfer is completed anyways. This allows us to flush on read in emergency situations, but still write the new data over the flushed data. Improves performance on Xenoblade 2 and DE, which was flushing buffer data on the GPU thread when trying to write compute data. May improve performance in other games that write SSBOs from compute, and update data in the same/nearby pages often. Super Smash Bros Ultimate should probably be tested to make sure the vertex explosions haven't returned, as I think that's what this AdvanceSequence was for. * ForceDirty before write, to make sure data does not flush over the new write		2021-09-19 15:09:53 +02:00
..
InlineToMemoryClass.cs	Fast path for Inline2Memory buffer write that skips write tracking (#2624)	2021-09-19 15:09:53 +02:00
InlineToMemoryClassState.cs	Separate GPU engines and make state follow official docs (part 1/2) (#2422)	2021-07-07 20:56:06 -03:00