madvise和fadvise的区别

最新推荐文章于 2025-05-13 16:48:17 发布

转载最新推荐文章于 2025-05-13 16:48:17 发布 · 4.4k 阅读

linux 专栏收录该内容

4 篇文章

订阅专栏

本文详细解析了madvise与posix_fadvise这两个系统调用的不同之处及应用场景。madvise用于向内核提供有关现有内存区域的使用建议，而fadvise则针对文件缓存给出提示。文章还介绍了它们在匿名内存映射和文件映射中的使用区别。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

madvise() and posix_fadvise() are not synonymous. madvise() tells the kernel (give advise) what to do with existing memory region while fadvise() tells the kernel what to do with cached (or future cache) of a file data.

For example, if you mmap() anonymous region you should use madvise() to hint the kernal not to swap out (MADV_RANDOM) or to swap out only after access. (MADV_SEQUENTIAL)

If you mmap() a file, or part of a file, you can use either madvise() or fadvise() to hint the kernel to readahead for you (MADV_WILLNEED) or to free that cache (MADV_DONTNEED) or to free after access (POSIX_FADV_NOREUSE, fadvise() only) in additional to the above.

If you use file without mapping the data to your process memory (without using mmap()), you should use fadvise() only. madvise() has no meaning.

As far as kernel subsystem, in linux, it is the same subsystem, simply different ways to refer to memory pages and file cache. Please note that those are only hints and when memory is in dire, the kernel might decide to swap out or reuse cached data despite the hint. Only mlock() and mlockall() can prevent that.

In your case, not giving any hint may help, especially if some pages are being read more than other, since the kernel will figure out which pages are "hot" and will attempt to keep in memory.