| 20 Apr 2025 |
 Andrew | and yet... swap state uses 8.4 GiB? what? | 16:06:42 |
| Andrew | at this point I just don't know anything | 16:07:01 |
 K900 | /proc/allocinfo doesn't track used memory | 16:07:06 |
| K900 | It tracks allocations | 16:07:10 |
| K900 | So whenever any memory is allocated, it will be tracked | 16:07:19 |
| K900 | It doesn't matter if it's backed by physical RAM or swap or anything else | 16:07:33 |
| Andrew | so... are tracked allocations never get erased? | 16:07:47 |
| K900 | And what it's backed by will change over time | 16:07:40 |
| K900 | No, they can be deallocated | 16:07:56 |
| K900 | But that file does not track "RAM" or "swap" | 16:08:26 |
| K900 | It tracks virtual memory, effectively | 16:08:33 |
| Andrew | No, I mean stuff from /proc/allocinfo doesn't get erased? | 16:09:19 |
| K900 | It does | 16:09:32 |
| Andrew | why it says swap state is so high if there is no swap now? will it ever stop showing it? | 16:09:53 |
| Andrew | * why it says swap state is so high if there is no swap now? will it ever stop showing swap state allocations? | 16:10:03 |
| Andrew | does it track with a delay or something? | 16:10:39 |
| K900 | No | 16:10:41 |
| K900 | When you disable a swap device, the pages stored on it don't go poof | 16:11:05 |
| K900 | They get moved to RAM | 16:11:07 |
| K900 | These are likely those pages | 16:11:12 |
| Andrew | uhh, but how can I make them go poof? | 16:11:38 |
| K900 | You can't | 16:11:52 |
| K900 | Because something will use those pages | 16:11:58 |
| Andrew | Redacted or Malformed Event | 16:12:11 |
| Andrew | sadge | 16:12:20 |
| K900 | You can reboot your system | 16:12:26 |
| K900 | Then you won't have any pages to be evacuated from swap space | 16:12:40 |
| K900 | Or at least a lot less of them | 16:12:52 |
| K900 | Ideally you would disable swap in your config, and then reboot | 16:13:04 |
| K900 | So there's nowhere to swap things out to | 16:13:09 |
