A read-only warm-up pass and NUMA first-touch

Trying to work around NUMA locality problems, a team has each worker thread run a 'warm-up' pass that only READS its portion of a large calloc()'d buffer before the real hot loop begins, believing this read pass will establish first-touch locality on that worker's own NUMA node (each worker is pinned to a different node). In production, workers still see the remote-NUMA-node access penalty in the hot loop, as if the warm-up pass never happened. On a typical modern Linux kernel/x86-64, why doesn't a read-only pass establish first-touch locality here?

warmup.cpp
// Each worker thread, pinned to its own NUMA node, does this before the hot loop:
volatile int sink;
for (size_t i = start; i < end; i += page_size / sizeof(int)) {
    sink = buf[i]; // read-only "warm-up", believed to establish first-touch locality
}
// ... hot loop follows, reading and writing buf[start..end) ...

43 of 53 in Operating Systems