Repository navigation
Conversation
|
Sparse guest release milestone pushed as biosed/ProjectReLink@3c64b03. This records exact sparse-allocation runs, batches safe VK_NULL_HANDLE unbinds after a queue drain, frees whole dead imported allocations, clears residency bits, and lets the existing host gap release punch pages afterward. The primary bookkeeping allocation is bounded to one sparse block. Gates: device-free sparse/range/import suites pass locally and with the BC-250 clang 22 toolchain; full renderer compile/link passes. Candidate relink_vk.so SHA-256: aa6aab9e1ac98f3fe9864429ee126c04e30014e1bc40e21b5c66da85718286c0. Guarded hardware route is next; PR remains draft pending those results. |
|
Guarded BC-250 hardware route for 3c64b03 completed under 5.25 GiB MemoryHigh / 7.5 GiB MemoryMax / 2 GiB swap / 5 minute cap. No crash, Vulkan error, unbind failure, or host-memory guard trip. The route did not reach an allocation eligible for this change: the game had freed only 26 MiB of address regions, and host telemetry reported 0 MiB of those held under GPU imports. Accordingly there were 0 sparse releases (and 0 failed releases). This corrects the current bottleneck diagnosis: late GTT flattened around 3.779 GiB while live scene construction stalled under reclaim and virtual-core starvation; stale sparse imports are not the source of this particular peak. Exact extrema: cgroup 5,707,792,384 B; swap 2,147,483,648 B; GTT 3,820,539,904 B; shmem 5,073,768,448 B; minimum MemAvailable 4,443,680 KiB; 57 C; PSI some +112.1 s. Evidence hashes: log 3c52124906cae1ecbfb1844e897a72971c744b600fa12a80daf27be74ffbcdc6, metrics 47bfbc66a721a5b11fe1f4da010ad3375812c5f1851c0e91587242af7ec22d2c. PR remains draft: the mechanism compiled and behaved conservatively, but its intended release path still needs a route or isolated Vulkan harness that actually makes an imported sparse allocation dead. |
|
Follow-up checkpoint The native helper now mirrors every replaced lifted Verified:
A same-profile guarded hardware A/B is next; no performance claim yet. |
|
Hardware-verified follow-up Same-profile BC-250 guarded comparison, with commit
Both runs stopped by the independent |
|
BC250 hardware milestone at 0087623: integrated/configured texture allowance now drives ASTC BC3 and staging retention. Pinned BC250 toolchain passed test_texture_memory_policy plus the four sparse/scheduler fixtures; full candidate build completed with 0 compile failures. Same guarded profile/limits reached upload #543 and 41M native-name searches versus #513 and 29M before, with 0 vcore escapes and 0 Optimize asked. Peak GTT was 4,459,634,688 B versus 4,509,126,656 B. The unchanged 4 GiB host-availability guard still stopped at ~2m because shared-memory/commit pressure remains the next boundary; Plasma/KDE Connect were restored. |
|
BC250 sparse-memory milestone: 93db628 splits aligned sparse guest runs across the kernel udmabuf byte/extent limits instead of falling back to dense imports; 6ec1614 zeros only allocated memfd extents when released guest ranges overlap GPU imports, preserving untouched holes. Six device-free fixtures pass on both local and pinned BC250 toolchains; full candidate build completed with 0 failures. Identical guarded hardware run: 4 oversized pools split successfully, 0 oversize failures, 0 dense fallbacks, 0 vcore escapes, 0 Optimize asked, upload #726 / 43.4M searches versus #543 / 41M before. Peak anonymous RSS fell 1,951,028 -> 739,832 KiB, swap 2,078,121,984 -> 1,510,477,824 B, and cgroup PSI 2.50 -> 1.24 s. Desktop restored after the 4 GiB host-floor guard. |
Use SEEK_DATA on the native Linux guest memfd before scanning a large texture for zeroes. A wholly unallocated range already reads as zero, so clear the Vulkan image without instantiating every shmem page. Keep the helper in the host sparse-file boundary and make it an explicit renderer build dependency. BC-250 run 19 recognized the 288 MiB and 32 MiB shadow targets in 0.3 ms and 0.1 ms, versus about 1.1 s plus 320 MiB of resident shmem in run 18.
|
BC-250 guarded hardware A/B for a3333b2:
Evidence remains outside git under the BC-250 run21 logs/screenshots. |
|
Milestone BC-250 guarded A/B: title movie remained 57–60 FPS; |
|
Milestone Validation: sparse range/file fixtures PASS; full Vulkan-only Linux build compiled 188 files with 0 failures. BC-250 guarded run29 with renderer hash |
|
Milestone update: This removes a measured 2.6 s |
|
Thanks a lot for this, and for the detailed BC-250 notes: they're useful well beyond Linux. I've read through it. It can't go in as one piece yet, and here is what would let the parts move. Scope. This started as an opt-in Linux sparse-import prototype, but it now also changes things every Windows player gets: the storage-buffer rule for fragment stages, giving up the virtual core around six renderer calls and the video decoder, the integrated-GPU texture budget, and
Windows impact. Anything under
Small things. The suyu Happy to keep this open as a draft while the sparse work goes on. |
Adds an opt-in RX_VK_SPARSE_GUEST Linux path using strict non-resident sparse-buffer semantics, memfd extent discovery, UDMABUF_CREATE_LIST imports, and host gap release. The normal complete-import path remains the fallback.
Tests:
Current hardware finding: this reduces early committed memory and preserves rendering, but blocks remain bound for the pool lifetime. A 111-second Kokiri load still reached the 4 GiB host safety floor, 2 GiB cgroup swap, and roughly 4.25 GB GTT, so this is intentionally a draft prototype rather than a claimed memory fix. DirectMesh submission churn is being investigated separately.