linux free 命令中的 buffer & free
2015-06-02 15:27
369 查看
Short answer: Cached is
the size of the page cache. Buffers is
the size of in-memory block I/O buffers. Cached matters; Buffers is
largely irrelevant.
Long answer: Cached is
the size of the Linux page cache, minus the memory in the swap cache, which is represented by SwapCached (thus
the total page cache size is Cached + SwapCached).
Linux performs all file I/O through the page cache. Writes are implemented as simply marking as dirty the corresponding pages in the
page cache;
the flusher threads then periodically write back to disk any dirty pages. Reads are implemented by returning the data from the page cache; if the data is not yet in the cache, it is first populated. On a modern Linux system, Cached can
easily be several gigabytes. It will shrink only in response to memory pressure. The system will purge the page cache along with swapping data out to disk to make available more memory as needed.
Buffers are
in-memory block I/O buffers. They are relatively short-lived. Prior to Linux kernel version 2.4, Linux had separate page and buffer caches. Since 2.4, the page and buffer cache are unified and Buffers is
raw disk blocks not represented in the page cache—i.e., not file data. The Buffers metric
is thus of minimal importance. On most systems, Buffers is
often only tens of megabytes.
the size of the page cache. Buffers is
the size of in-memory block I/O buffers. Cached matters; Buffers is
largely irrelevant.
Long answer: Cached is
the size of the Linux page cache, minus the memory in the swap cache, which is represented by SwapCached (thus
the total page cache size is Cached + SwapCached).
Linux performs all file I/O through the page cache. Writes are implemented as simply marking as dirty the corresponding pages in the
page cache;
the flusher threads then periodically write back to disk any dirty pages. Reads are implemented by returning the data from the page cache; if the data is not yet in the cache, it is first populated. On a modern Linux system, Cached can
easily be several gigabytes. It will shrink only in response to memory pressure. The system will purge the page cache along with swapping data out to disk to make available more memory as needed.
Buffers are
in-memory block I/O buffers. They are relatively short-lived. Prior to Linux kernel version 2.4, Linux had separate page and buffer caches. Since 2.4, the page and buffer cache are unified and Buffers is
raw disk blocks not represented in the page cache—i.e., not file data. The Buffers metric
is thus of minimal importance. On most systems, Buffers is
often only tens of megabytes.
相关文章推荐
- Android之使用Http协议实现文件上传功能
- 网马生成器 MS Internet Explorer XML Parsing Buffer Overflow Exploit (vista) 0day
- 分析Cache 在 Ruby China 里面的应用情况
- asp 页面允许CACHE的方法
- web 应用中常用的各种 cache详解
- 揭秘SQL Server 2014有哪些新特性(2)-固态硬盘 Buffer Pool(缓冲池) 扩展
- php中ob(Output Buffer 输出缓冲)函数使用方法
- php中mysql操作buffer用法详解
- ASP javascript Application对象的Contents和StaticObjects做Cache的一些经验
- ASP.NET笔记之 viewstate与cache的使用
- 解决php中Cannot send session cache limiter 的问题的方法
- IE cache缓存 所带来的问题收藏
- 用PHP的ob_start() 控制您的浏览器cache
- Asp.Net中Cache操作类实例详解
- IIS设置CACHE过期时间的教程
- php cache类代码(php数据缓存类)
- Protocol Buffer技术深入理解(C++实例)
- ASP.NET Cache的一些总结分享
- mysqldump造成Buffer Pool污染的研究
- 对于mysql的query_cache认识的误区