If you like BoxMatrix then please contribute Supportdata, Supportdata2, Firmware and/or Hardware (get in touch).
My metamonk@yahoo.com is not reachable by me since years. Please use hippie2000@webnmail.de instead.
0
U
Property:meminfo (procfs)
From BoxMatrix
| BoxMatrix >> System >> meminfo (procfs) | @ BoxMatrix - IRC-Chat - Translate: de es fr it nl pl |
| News | Selectors | Models | Accessories | Components | Environment | Config | Commands | System | Webif | Software | Develop | Lexicon | Community | Project | Media |
| Devices | Filesystems | Partitions | Sockets | Netlink | Pipes | Interfaces | Bridges | Ports | Events | Sources | Sinks | AVMIPC | Processes | Watchdogs | Memory | Slab | Vmalloc | ProcFS | SysFS | Research |
 |
Name-Collision - multiple objects in this wiki use the name meminfo!
|
Procfs-Object
| Procfs-Object: | meminfo (procfs) - type File | Wiki | Freetz | IPPF | whmf | AVM | Web |
| Location: | System >> Proc-Filesystem - Origin: Linux | ||||||
| Path: | /proc | ||||||
| Properties: | Firmware: 4.07 - 7.90 - Kernel (perm): 2.4.17 (r), 2.6.13.1 (r), 2.6.28.10 (r), 2.6.32.21 (r), 2.6.32.60 (r), 2.6.32.61 (r), 2.6.39.4 (r), 3.10.107 (r), 3.10.73 (r), 4.1.38 (r), 4.1.52 (r), 4.19.183 (r), 4.4.271 (r), 4.4.60 (r), 4.9.198 (r), 4.9.218 (r), 4.9.250 (r), 4.9.325 (r) | ||||||
| Function: | Distribution and utilization of memory. | ||||||
Goto: Dependencies - Model-Matrix - Help Supportdata2 - SMW-Browser
Details
meminfo provides information about distribution and utilization of memory.
Supportdata2 includes meminfo in the Meminfo section since sd2-09.
In Supportdata-Probes it is included since fw 4.52. The Memory-Info section uses this data.
Excerpt from the Kernel.org /proc filesystem documentation:
/proc/meminfo: Provides information about distribution and utilization of memory. This varies by architecture and compile options. The following is from a 16GB PIII, which has highmem enabled. You may not have all of these fields. > cat /proc/meminfo MemTotal: 16344972 kB MemFree: 13634064 kB MemAvailable: 14836172 kB Buffers: 3656 kB Cached: 1195708 kB SwapCached: 0 kB Active: 891636 kB Inactive: 1077224 kB HighTotal: 15597528 kB HighFree: 13629632 kB LowTotal: 747444 kB LowFree: 4432 kB SwapTotal: 0 kB SwapFree: 0 kB Dirty: 968 kB Writeback: 0 kB AnonPages: 861800 kB Mapped: 280372 kB Shmem: 644 kB KReclaimable: 168048 kB Slab: 284364 kB SReclaimable: 159856 kB SUnreclaim: 124508 kB PageTables: 24448 kB NFS_Unstable: 0 kB Bounce: 0 kB WritebackTmp: 0 kB CommitLimit: 7669796 kB Committed_AS: 100056 kB VmallocTotal: 112216 kB VmallocUsed: 428 kB VmallocChunk: 111088 kB Percpu: 62080 kB HardwareCorrupted: 0 kB AnonHugePages: 49152 kB ShmemHugePages: 0 kB ShmemPmdMapped: 0 kB MemTotal: Total usable ram (i.e. physical ram minus a few reserved bits and the kernel binary code) MemFree: The sum of LowFree+HighFree MemAvailable: An estimate of how much memory is available for starting new applications, without swapping. Calculated from MemFree, SReclaimable, the size of the file LRU lists, and the low watermarks in each zone. The estimate takes into account that the system needs some page cache to function well, and that not all reclaimable slab will be reclaimable, due to items being in use. The impact of those factors will vary from system to system. Buffers: Relatively temporary storage for raw disk blocks shouldn't get tremendously large (20MB or so) Cached: in-memory cache for files read from the disk (the pagecache). Doesn't include SwapCached SwapCached: Memory that once was swapped out, is swapped back in but still also is in the swapfile (if memory is needed it doesn't need to be swapped out AGAIN because it is already in the swapfile. This saves I/O) Active: Memory that has been used more recently and usually not reclaimed unless absolutely necessary. Inactive: Memory which has been less recently used. It is more eligible to be reclaimed for other purposes HighTotal: HighFree: Highmem is all memory above ~860MB of physical memory Highmem areas are for use by userspace programs, or for the pagecache. The kernel must use tricks to access this memory, making it slower to access than lowmem. LowTotal: LowFree: Lowmem is memory which can be used for everything that highmem can be used for, but it is also available for the kernel's use for its own data structures. Among many other things, it is where everything from the Slab is allocated. Bad things happen when you're out of lowmem. SwapTotal: total amount of swap space available SwapFree: Memory which has been evicted from RAM, and is temporarily on the disk Dirty: Memory which is waiting to get written back to the disk Writeback: Memory which is actively being written back to the disk AnonPages: Non-file backed pages mapped into userspace page tables HardwareCorrupted: The amount of RAM/memory in KB, the kernel identifies as corrupted. AnonHugePages: Non-file backed huge pages mapped into userspace page tables Mapped: files which have been mmaped, such as libraries Shmem: Total memory used by shared memory (shmem) and tmpfs ShmemHugePages: Memory used by shared memory (shmem) and tmpfs allocated with huge pages ShmemPmdMapped: Shared memory mapped into userspace with huge pages KReclaimable: Kernel allocations that the kernel will attempt to reclaim under memory pressure. Includes SReclaimable (below), and other direct allocations with a shrinker. Slab: in-kernel data structures cache SReclaimable: Part of Slab, that might be reclaimed, such as caches SUnreclaim: Part of Slab, that cannot be reclaimed on memory pressure PageTables: amount of memory dedicated to the lowest level of page tables. NFS_Unstable: NFS pages sent to the server, but not yet committed to stable storage Bounce: Memory used for block device "bounce buffers" WritebackTmp: Memory used by FUSE for temporary writeback buffers 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 = ([total RAM pages] - [total huge TLB pages]) * overcommit_ratio / 100 + [total swap pages] 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 show up as using 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: total size of vmalloc memory area VmallocUsed: amount of vmalloc area which is used VmallocChunk: largest contiguous block of vmalloc area which is free Percpu: Memory allocated to the percpu allocator used to back percpu allocations. This stat excludes the cost of metadata.
Dependencies
Daily updated index of all dependencies of this object. Last update: GMT.
A ** in the Mod column marks info from Supportdata2 probes, which will always stay incomplete.
A - in the Mod column marks manual research, the Firmware then shows where the Object occurs, not the Relation.
| Relation | Typ | Object | Mod | Firmware | Info | Origin |
|---|---|---|---|---|---|---|
| 0 dependencies for this object | ||||||
Model-Matrix
Daily updated index of the presence, path and size of this object for each model. Last update: 2024-12-03 05:13 GMT.
Showing all models using this object. Click any column header (click-wait-click) to sort the list by the respective data.
The (main/scrpn/boot/arm/prx/atom/rtl) label in the Model column shows which CPU is meant for Multi-Linux models.
Note that this list comes from Supportdata2 probes, which can have arbitrary settings and come from different firmware versions.
It doesn't say much if a model is not listed here. It may be a missing supportdata2 file or just a disabled feature.
| Model | Firmware | Path | Kernel (perm) |
|---|---|---|---|
| FRITZ!Box SL WLAN | 4.34 | /proc | 2.6.13.1 (r) |
| FRITZ!Box WLAN 3020 | 4.34 | /proc | 2.6.13.1 (r) |
| FRITZ!Box WLAN 3050 | 4.07 | /proc | 2.4.17 (r) |
| FRITZ!Box WLAN 3070 | 4.15 | /proc | 2.4.17 (r) |
| FRITZ!Box 3490 | 7.30 | /proc | 3.10.107 (r) |
| FRITZ!Box 4020 | 7.01 | /proc | 4.4.60 (r) |
| FRITZ!Box 4060 | 7.30 - 7.39 | /proc | 4.4.271 (r), 4.4.60 (r) |
| FRITZ!Box 5490 | 7.29 | /proc | 3.10.107 (r) |
| FRITZ!Box 5590 Fiber (main) | 7.29 | /proc | 4.4.60 (r) |
| FRITZ!Box 6360 Cable | 5.20 | /proc | 2.6.28.10 (r) |
| FRITZ!Box 6430 Cable (arm) | 7.29 | /proc | 2.6.39.4 (r) |
| FRITZ!Box 6430 Cable (atom) | 7.29 | /proc | 2.6.39.4 (r) |
| FRITZ!Box 6490 Cable (arm) | 7.29 - 7.39 | /proc | 2.6.39.4 (r) |
| FRITZ!Box 6490 Cable (atom) | 7.29 - 7.39 | /proc | 2.6.39.4 (r) |
| FRITZ!Box 6660 Cable (atom) | 7.29 | /proc | 4.9.250 (r) |
| FRITZ!Box 6850 LTE | 7.39 | /proc | 4.4.60 (r) |
| FRITZ!Box 6850 5G | 7.39 | /proc | 4.4.60 (r) |
| FRITZ!Box Fon WLAN 7050 | 4.33 | /proc | 2.6.13.1 (r) |
| FRITZ!Box Fon WLAN 7140 | 4.33 | /proc | 2.6.13.1 (r) |
| FRITZ!Fon 7150 | 4.72 | /proc | 2.6.13.1 (r) |
| FRITZ!Box Fon WLAN 7240 | 6.06 | /proc | 2.6.32.60 (r) |
| FRITZ!Box 7272 | 6.88 | /proc | 2.6.32.61 (r) |
| FRITZ!Box Fon WLAN 7320 | 6.55 | /proc | 2.6.32.61 (r) |
| FRITZ!Box 7362 SL | 7.12 | /proc | 3.10.107 (r) |
| FRITZ!Box Fon WLAN 7390 | 6.04 | /proc | 2.6.28.10 (r) |
| FRITZ!Box 7412 | 6.87 | /proc | 3.10.73 (r) |
| FRITZ!Box 7430 | 7.29 | /proc | 3.10.107 (r) |
| FRITZ!Box 7490 | 7.29 - 7.51 | /proc | 3.10.107 (r) |
| FRITZ!Box 7510 | 7.30 | /proc | 4.4.60 (r) |
| FRITZ!Box 7520 | 7.29 - 7.50 | /proc | 4.4.271 (r), 4.4.60 (r) |
| FRITZ!Box 7520 v2 | 7.31 | /proc | 4.4.60 (r) |
| FRITZ!Box 7530 | 7.39 | /proc | 4.4.271 (r) |
| FRITZ!Box 7530 AX | 7.31 - 7.51 | /proc | 4.1.52 (r), 4.19.183 (r) |
| FRITZ!Box 7581 | 7.17 | /proc | 4.1.38 (r) |
| FRITZ!Box 7590 | 7.57 - 7.90 | /proc | 4.9.325 (r) |
| FRITZ!Box 7590 AX | 7.31 - 7.39 | /proc | 4.9.198 (r), 4.9.218 (r) |
| FRITZ!Smart Gateway | 7.57 - 7.58 | /proc | 4.4.271 (r) |
| FRITZ!Repeater 1200 AX | 7.30 - 7.39 | /proc | 4.4.60 (r) |
| FRITZ!WLAN Repeater 1750E | 7.29 | /proc | 4.4.60 (r) |
| FRITZ!Repeater 6000 | 7.29 - 7.39 | /proc | 4.4.60 (r) |
| Speedport W 504V MK | 5.04 | /proc | 2.6.32.21 (r) |
| 41 models use this object | |||
Help Supportdata2
The data in this article is incomplete since it was manually collected using the Supportdata2 project.
Unlike the Supportdata-Probes which have been collected for years Supportdata2 is brand new and only has a few probes.
If you have access to a shell then please help to extend the Supportdata2 collection to improve this data.
It's easy and it's done in minutes. Please send created data as an Email attachment to the address listed here. Thanks!
