From 28d8d47eb38b9e82a51b69a6c4d4da98d7b102ea Mon Sep 17 00:00:00 2001 From: Tobim6 <102646588+Tobim6@users.noreply.github.com> Date: Thu, 12 Nov 2026 16:21:50 +0100 Subject: [PATCH] Add NX2NAVI_FLUSH_SKIP_CLEAN: flushed ranges upload only the pages the CPU wrote. On 0.6.1 the mirror sync already leaves flush ranges of write-watched pools uncopied (0101a87), which covers what this did; the key stays known and does nothing. Co-Authored-By: Claude Opus 5.5 --- runtime/vk_memory.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/runtime/vk_memory.c b/runtime/vk_memory.c index 6ea6d530..0781cb0d 100644 --- a/runtime/vk_memory.c +++ b/runtime/vk_memory.c @@ -2042,6 +2042,9 @@ static int cregions; static PlatMutex flush_lock = PLAT_MUTEX_INIT; static int flush_cap = FLUSH_RANGES; // ranges a pool keeps; 1 with NX2NAVI_FLUSH_SPAN=1 static int flush_upload; // NX2NAVI_FLUSH_UPLOAD=1: flush ranges are copied where the write watch sees them too +// NX2NAVI_FLUSH_SKIP_CLEAN (flush_clean_bytes in the 0.5.0 and 0.6.0 fixes: flushed ranges upload only the pages the CPU +// wrote) is this default since 0.6.1: a flush range of a write-watched pool is not copied at all; the key stays known so an +// nx2navi.ini that sets it reads without a warning, and does nothing. typedef struct { uint64_t subs, syncs, upload_bytes, upload_copies, first_n, first_bytes, wb_bytes, wb_copies, wb_ranges;