You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If vmtouch.c is compiled with gcc -O2, evict succeeds by calling posix_fadvise.
But with gcc -O0, evict fails and mincore shows that memory is still used.
What's the difference between -O2 and -O0 for posix_fadvise ?
If use mmap, mlock, munlock sequentially, then call posix_fadvise and mincore shows that memory is still used.
If mlock and munlock is skipped, posix_fadvise succeeds.
I know that posix_fadivse is async, but how does lock affects it ?
Thanks !
The text was updated successfully, but these errors were encountered:
If vmtouch.c is compiled with gcc -O2, evict succeeds by calling posix_fadvise.
But with gcc -O0, evict fails and mincore shows that memory is still used.
What's the difference between -O2 and -O0 for posix_fadvise ?
If use mmap, mlock, munlock sequentially, then call posix_fadvise and mincore shows that memory is still used.
If mlock and munlock is skipped, posix_fadvise succeeds.
I know that posix_fadivse is async, but how does lock affects it ?
Thanks !
The text was updated successfully, but these errors were encountered: