5a39d3c4a1
I did this on ncbuffer2 when we were using it for LDN 3, but I noticed that it can apply to the current buffer manager too, and it's an easy performance win. The only buffer access that can come from another thread is the overlap search for buffers that have been unmapped. Everything else, including modifications, come from the main GPU thread. That means we only need to lock the range list when it's being modified, as that's the only time where we'll cause a race with the unmapped handler. This has a significant performance improvements in situations where FIFO is high, like the other two PRs. Joined together they give a nice boost (73.6 master -> 79 -> 83 fps in SMO). |
||
|---|---|---|
| .. | ||
| Buffer.cs | ||
| BufferBounds.cs | ||
| BufferCache.cs | ||
| BufferCacheEntry.cs | ||
| BufferManager.cs | ||
| BufferModifiedRangeList.cs | ||
| BufferTextureBinding.cs | ||
| CounterCache.cs | ||
| GpuRegionHandle.cs | ||
| IndexBuffer.cs | ||
| MemoryManager.cs | ||
| MultiRangeWritableBlock.cs | ||
| PhysicalMemory.cs | ||
| PteKind.cs | ||
| UnmapEventArgs.cs | ||
| VertexBuffer.cs | ||