adb shell cat /proc/meminfo



以下引用自:http://blog.csdn.net/huanghq1984/article/details/6029715

MemTotal: 所有可用RAM大小 (即物理内存减去一些预留位和内核的二进制代码大小)

MemFree: LowFree与HighFree的总和,被系统留着未使用的内存

Buffers: 用来给文件做缓冲大小

Cached: 被高速缓冲存储器(cache memory)用的内存的大小(等于 diskcache minus SwapCache ).

SwapCached:被高速缓冲存储器(cache memory)用的交换空间的大小已经被交换出来的内存,但仍然被存放在swapfile中。用来在需要的时候很快的被替换而不需要再次打开I/O端口。

Active: 在活跃使用中的缓冲或高速缓冲存储器页面文件的大小,除非非常必要否则不会被移作他用.

Inactive: 在不经常使用中的缓冲或高速缓冲存储器页面文件的大小,可能被用于其他途径.

HighTotal:

HighFree: 该区域不是直接映射到内核空间。内核必须使用不同的手法使用该段内

LowTotal:

LowFree: 低位可以达到高位内存一样的作用,而且它还能够被内核用来记录一些自己的数据结构。

SwapTotal: 交换空间的总大小

SwapFree: 未被使用交换空间的大小

Dirty: 等待被写回到磁盘的内存大小。

Writeback: 正在被写回到磁盘的内存大小。

AnPages:未映射页的内存大小

Mapped: 设备和文件等映射的大小。

Slab: 内核数据结构缓存的大小,可以减少申请和释放内存带来的消耗。

SReclaimable:可收回Slab的大小

SUnreclaim:不可收回Slab的大小(SUnreclaim+SReclaimable=Slab)

PageTables:管理内存分页页面的索引表的大小。

NFS_Unstable:不稳定页表的大小

Bounce:

CommitLimit: Based on the overcommit ratio ('vm.overcommit_ratio'),

this is the total amount of memory currently available to

be allocated on the system. This limit is only adhered to

if strict overcommit accounting is enabled (mode 2 in

'vm.overcommit_memory').

The CommitLimit is calculated with the following formula:

CommitLimit = ('vm.overcommit_ratio' * Physical RAM) + Swap

For example, on a system with 1G of physical RAM and 7G

of swap with a `vm.overcommit_ratio` of 30 it would

yield a CommitLimit of 7.3G.

For more details, see the memory overcommit documentation

in vm/overcommit-accounting.

Committed_AS: The amount of memory presently allocated on the system.

The committed memory is a sum of all of the memory which

has been allocated by processes, even if it has not been

"used" by them as of yet. A process which malloc()'s 1G

of memory, but only touches 300M of it will only show up

as using 300M of memory even if it has the address space

allocated for the entire 1G. This 1G is memory which has

been "committed" to by the VM and can be used at any time

by the allocating application. With strict overcommit

enabled on the system (mode 2 in 'vm.overcommit_memory'),

allocations which would exceed the CommitLimit (detailed

above) will not be permitted. This is useful if one needs

to guarantee that processes will not fail due to lack of

memory once that memory has been successfully allocated.

VmallocTotal: 可以vmalloc虚拟内存大小

VmallocUsed: 已经被使用的虚拟内存大小。

VmallocChunk: largest contigious block of vmalloc area which is free


更多相关文章

  1. android native内存泄漏检测原理
  2. 使用showmap分析android进程内存占用情况
  3. Android(安卓)OpenGL相关
  4. Android(安卓)让adb logcat打印内核调试信息
  5. Android(安卓)Studio 一些使用经验 - 传说之美
  6. Android之App应用内存分配
  7. VMRuntime.getRuntime().setMinimumHeapSize(4 * 1024 * 1024);
  8. android values-v11和values-v14文件夹是干啥的?
  9. LeakCanary的使用

随机推荐

  1. 执行Django数据库值的计算:视图。py或Jav
  2. 通过AJAX加载内容和预加载图像?
  3. 使用JQuery从外部文件中通过id选择器获取
  4. 使用jQuery更新textarea值更改的文本
  5. 是否每次都可能分离内容、表示和行为?
  6. jquery向Django后台发送数组
  7. 将JavaScript对象作为Dictionary 传递给C
  8. 如何防止缓存.NET JSON源
  9. 如何在用户选择操作后获取当前日期和时间
  10. jquery内部实现原理分析