Sponsored Content
Full Discussion: MemFree from /proc/meminfo
Top Forums Shell Programming and Scripting MemFree from /proc/meminfo Post 302981921 by michaelrozar17 on Wednesday 21st of September 2016 09:42:28 AM
Old 09-21-2016
MemFree from /proc/meminfo

From the following /proc/meminfo output only ~2GB is free out of total 250GB, but Cached is 194630300 kB. My customer is concerned over the very little memory showing as free. Kindly shed some light if the free memory available in this situation is some thing we need to worry or can we take it as expected behavior of Linux kernel - as most of them are cached.
Linux 2.6.39-400.277.1.el6uek.x86_64
Code:
MemTotal:       264082720 kB
MemFree:         2114036 kB
Buffers:          417188 kB
Cached:         194630300 kB
SwapCached:          172 kB
Active:         12577096 kB
Inactive:       189334136 kB
Active(anon):    6788124 kB
Inactive(anon):   221452 kB
Active(file):    5788972 kB
Inactive(file): 189112684 kB
Unevictable:      494788 kB
Mlocked:          494836 kB
SwapTotal:      25165820 kB
SwapFree:       25160384 kB
Dirty:              2008 kB
Writeback:           108 kB
AnonPages:       7402208 kB
Mapped:           260780 kB
Shmem:              1012 kB
Slab:            1532520 kB
SReclaimable:    1201976 kB
SUnreclaim:       330544 kB
KernelStack:       19200 kB
PageTables:       385236 kB
NFS_Unstable:          0 kB
Bounce:                0 kB
WritebackTmp:          0 kB
CommitLimit:    130992780 kB
Committed_AS:   12763688 kB
VmallocTotal:   34359738367 kB
VmallocUsed:     1178180 kB
VmallocChunk:   34224213544 kB
HardwareCorrupted:     0 kB
HugePages_Total:   25600
HugePages_Free:    14820
HugePages_Rsvd:        0
HugePages_Surp:        0
Hugepagesize:       2048 kB
DirectMap4k:        8192 kB
DirectMap2M:     2023424 kB
DirectMap1G:    266338304 kB

 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

/proc 100%

The df/bdf command shows /proc 100% full all the time. What does /proc contain? and why 100% all the time even on a new setup. (1 Reply)
Discussion started by: asutoshch
1 Replies

2. UNIX for Dummies Questions & Answers

about /proc

hi, we all know /proc is about the information of active process, I have just read an artical which said you can use /proc/cpuinfo, /proc/net./proc/meminfo etc. to know about some hardware information .But I want to know how to use with command line? (1 Reply)
Discussion started by: fuqiang1976
1 Replies

3. UNIX for Advanced & Expert Users

/proc

/proc is filing up my root filesystem. Can you delete any of the4 ID numbers out of /proc. Please help me. (3 Replies)
Discussion started by: aojmoj
3 Replies

4. UNIX for Dummies Questions & Answers

proc

Hi, What are the various way's to fix /proc folder in redhat linux 7.2 and how to verify /proc folder is proper or croupted? Thank in advance Bache Gowda (7 Replies)
Discussion started by: bache_gowda
7 Replies

5. Linux

Meminfo

This server is running slowly This is our mail server What is 'cached' in /proc/meminfo ? Can I minimize the usage of cached ? (1 Reply)
Discussion started by: dipanrc
1 Replies

6. Programming

Need help ! SQL and Proc *C

:) hi all ! Please help me When I select data from oracle with proc * C prog. I count the number of rows For example the total rows is 1000000 but the number of result return is a limit number 5000 for ex So How can I know this limit (5 Replies)
Discussion started by: iwbasts
5 Replies

7. UNIX for Dummies Questions & Answers

_/proc/stat vs /proc/uptime

Hi, I am trying to calculate the CPU Usage by getting the difference between the idle time reported by /proc/stat at 2 different intervals. Now the 4th entry in the first line of /proc/stat will give me the 'idle time'. But I also came across /proc/uptime that gives me 2 entries : 1st one as the... (0 Replies)
Discussion started by: coderd
0 Replies

8. Filesystems, Disks and Memory

Buffer Cache Stats from /proc/meminfo

Hi, I am trying to understand the role of buffer cache in block I/O. I am monitoring /proc/meminfo, my question is does the value of 0 for 'buffers', mean that any subsequent disk read issued by a process, would get the data physically from the disk, and not an allocated buffer for the block? ... (1 Reply)
Discussion started by: jake24
1 Replies

9. UNIX for Dummies Questions & Answers

Regarding /proc

If you are adding the kernel module without any module parameter passing, it should print out following information to info1 file so that user can make read access to info1 file (via, for example, cat /proc/info1): • Processor type • Kernel version • Total number of the processes currently... (1 Reply)
Discussion started by: shekhar.huded
1 Replies

10. Shell Programming and Scripting

Awk and meminfo

I'm in the process of adding various data to my rrdtool setup, and one of the things i want ot monitor is the meminfo stuff. I have it running locally very well with the following: /usr/bin/rrdupdate /etc/rrdtool/192.168.43.254.mem.rrd --template \ used:free:buff:cached:swap N:`awk ' \ ... (2 Replies)
Discussion started by: Nunners
2 Replies
ALLOC_HUGEPAGES(2)					     Linux Programmer's Manual						ALLOC_HUGEPAGES(2)

NAME
alloc_hugepages, free_hugepages - allocate or free huge pages SYNOPSIS
void *alloc_hugepages(int key, void *addr, size_t len, int prot, int flag); int free_hugepages(void *addr); DESCRIPTION
The system calls alloc_hugepages() and free_hugepages() were introduced in Linux 2.5.36 and removed again in 2.5.54. They existed only on i386 and ia64 (when built with CONFIG_HUGETLB_PAGE). In Linux 2.4.20 the syscall numbers exist, but the calls fail with the error ENOSYS. On i386 the memory management hardware knows about ordinary pages (4 KiB) and huge pages (2 or 4 MiB). Similarly ia64 knows about huge pages of several sizes. These system calls serve to map huge pages into the process's memory or to free them again. Huge pages are locked into memory, and are not swapped. The key argument is an identifier. When zero the pages are private, and not inherited by children. When positive the pages are shared with other applications using the same key, and inherited by child processes. The addr argument of free_hugepages() tells which page is being freed: it was the return value of a call to alloc_hugepages(). (The memory is first actually freed when all users have released it.) The addr argument of alloc_hugepages() is a hint, that the kernel may or may not follow. Addresses must be properly aligned. The len argument is the length of the required segment. It must be a multiple of the huge page size. The prot argument specifies the memory protection of the segment. It is one of PROT_READ, PROT_WRITE, PROT_EXEC. The flag argument is ignored, unless key is positive. In that case, if flag is IPC_CREAT, then a new huge page segment is created when none with the given key existed. If this flag is not set, then ENOENT is returned when no segment with the given key exists. RETURN VALUE
On success, alloc_hugepages() returns the allocated virtual address, and free_hugepages() returns zero. On error, -1 is returned, and errno is set appropriately. ERRORS
ENOSYS The system call is not supported on this kernel. FILES
/proc/sys/vm/nr_hugepages Number of configured hugetlb pages. This can be read and written. /proc/meminfo Gives info on the number of configured hugetlb pages and on their size in the three variables HugePages_Total, HugePages_Free, Hugepagesize. CONFORMING TO
These calls are specific to Linux on Intel processors, and should not be used in programs intended to be portable. NOTES
These system calls are gone; they existed only in Linux 2.5.36 through to 2.5.54. Now the hugetlbfs file system can be used instead. Mem- ory backed by huge pages (if the CPU supports them) is obtained by using mmap(2) to map files in this virtual file system. The maximal number of huge pages can be specified using the hugepages= boot parameter. COLOPHON
This page is part of release 3.44 of the Linux man-pages project. A description of the project, and information about reporting bugs, can be found at http://www.kernel.org/doc/man-pages/. Linux 2007-05-31 ALLOC_HUGEPAGES(2)
All times are GMT -4. The time now is 04:54 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy