Sponsored Content
Top Forums UNIX for Advanced & Expert Users Command to check memory used or consumed by OS kernel Post 303000069 by sam@sam on Tuesday 4th of July 2017 01:49:52 AM
Old 07-04-2017
Command to check memory used or consumed by OS kernel

I am trying to check how much memory is consumed by OS Kernel using below command, Is this the correct command that I'm using

Code:
grep Slab /proc/meminfo

Output : Slab: 3106824 kB
IF I convert KB to GB, It means 2.9 GB of RAM is consumed


Below details for reference
Code:
  uname -a (6.8 santiago)
2.6.32-696.1.1.el6.x86_64 #1 SMP Tue Mar 21 12:19:18 EDT 2017 x86_64 x86_64 x86_64 GNU/Linux


Last edited by vbe; 07-04-2017 at 04:02 AM..
 

10 More Discussions You Might Find Interesting

1. Solaris

1. To know the Memory consumed by a process at a time

hello I am new to the UNIX I want to know what command is used 1.To know the Memory consumed by a process at a time . 2.To know the How many CPU's in a server. 3.To know the RAM size. 4.To know the Hard Disk size. (3 Replies)
Discussion started by: maheshkoushik
3 Replies

2. HP-UX

kernel, memory and patches information

I kind of forget easily. Is anyone remember the command to find kernel, memory and patches information of HPUX 11.0 machine? Thank you! (0 Replies)
Discussion started by: Teh Tiack Ein
0 Replies

3. AIX

Kernel use of real memory

Hello AIX gurues... In order to present the statistics of real memory usage I need to know how much real memory is used by the AIX 5L kernel. No the exact figures of course but some close to the reality. The AIX is running in a 7GB real machine, it has a HACMP configuration and my concern is... (1 Reply)
Discussion started by: daniels
1 Replies

4. UNIX for Advanced & Expert Users

the amount of memory consumed per user

Hi, under UNIX AIX how determine the amount of memory consumed per user ? Many thanks before. (1 Reply)
Discussion started by: big123456
1 Replies

5. Solaris

Command to check memory size

Hi, I am looking for acoomand on HP where by i can see the CPU increasing for a given process ... I know i can see this from top/prstat .. But it will give for all the processes - I want something like say ps where i can call it from a shell script a few times and check if it is has increased... (0 Replies)
Discussion started by: nano2
0 Replies

6. HP-UX

Order process by consumed memory

Hi! I am new to HP-UX. :o By using the command glance, I found the user memory usage was very high. I would like to know is there any command can show the process which consume most available memory ? (Just like the command top, but order by memory, not CPU) (1 Reply)
Discussion started by: alfredo
1 Replies

7. Shell Programming and Scripting

How can I obtain the consumed memory of a process?

Hi!!! how can I obtain the consumed memory of a process? nowadays i'm using ps -efo pid, pmem, comm,args .... but the information is in percentage, is that correct? so, i want to know how can obtain the consumed memory of a process in mb? thanks in advance! Richard (3 Replies)
Discussion started by: rcrutz_18
3 Replies

8. Red Hat

PAE kernel memory limit

What is the limit of LowMem and HighMem in PAE enable kernel. (2 Replies)
Discussion started by: hiten.r.chauhan
2 Replies

9. Solaris

Logging the memory consumed by a process with c/C++ without using proc

I need to log the size of physical/virtual memory consumed by any given given process using c/c++ code running on solaris and aix without using the proc filesystem. Please advise. (1 Reply)
Discussion started by: Manisha Paul
1 Replies

10. AIX

Process, PID and total memory consumed on AIX.

Hi, Below is the code snippet I use on Linux (Centos) to retrieve the Process Name, PID and memory consumed on Linux (Centos) host:- top -b -n 1 | awk -v date="$tdydate" -v ip="$ip" 'NR>7 {print date","ip","$12,","$1,","$10}' Any idea how the same can be retrieved on an AIX host? This... (1 Reply)
Discussion started by: Vipin Batra
1 Replies
LWRES_BUFFER(3) 						       BIND9							   LWRES_BUFFER(3)

NAME
lwres_buffer_init, lwres_buffer_invalidate, lwres_buffer_add, lwres_buffer_subtract, lwres_buffer_clear, lwres_buffer_first, lwres_buffer_forward, lwres_buffer_back, lwres_buffer_getuint8, lwres_buffer_putuint8, lwres_buffer_getuint16, lwres_buffer_putuint16, lwres_buffer_getuint32, lwres_buffer_putuint32, lwres_buffer_putmem, lwres_buffer_getmem - lightweight resolver buffer management SYNOPSIS
#include <lwres/lwbuffer.h> void lwres_buffer_init(lwres_buffer_t *b, void *base, unsigned int length); void lwres_buffer_invalidate(lwres_buffer_t *b); void lwres_buffer_add(lwres_buffer_t *b, unsigned int n); void lwres_buffer_subtract(lwres_buffer_t *b, unsigned int n); void lwres_buffer_clear(lwres_buffer_t *b); void lwres_buffer_first(lwres_buffer_t *b); void lwres_buffer_forward(lwres_buffer_t *b, unsigned int n); void lwres_buffer_back(lwres_buffer_t *b, unsigned int n); lwres_uint8_t lwres_buffer_getuint8(lwres_buffer_t *b); void lwres_buffer_putuint8(lwres_buffer_t *b, lwres_uint8_t val); lwres_uint16_t lwres_buffer_getuint16(lwres_buffer_t *b); void lwres_buffer_putuint16(lwres_buffer_t *b, lwres_uint16_t val); lwres_uint32_t lwres_buffer_getuint32(lwres_buffer_t *b); void lwres_buffer_putuint32(lwres_buffer_t *b, lwres_uint32_t val); void lwres_buffer_putmem(lwres_buffer_t *b, const unsigned char *base, unsigned int length); void lwres_buffer_getmem(lwres_buffer_t *b, unsigned char *base, unsigned int length); DESCRIPTION
These functions provide bounds checked access to a region of memory where data is being read or written. They are based on, and similar to, the isc_buffer_ functions in the ISC library. A buffer is a region of memory, together with a set of related subregions. The used region and the available region are disjoint, and their union is the buffer's region. The used region extends from the beginning of the buffer region to the last used byte. The available region extends from one byte greater than the last used byte to the end of the buffer's region. The size of the used region can be changed using various buffer commands. Initially, the used region is empty. The used region is further subdivided into two disjoint regions: the consumed region and the remaining region. The union of these two regions is the used region. The consumed region extends from the beginning of the used region to the byte before the current offset (if any). The remaining region the current pointer to the end of the used region. The size of the consumed region can be changed using various buffer commands. Initially, the consumed region is empty. The active region is an (optional) subregion of the remaining region. It extends from the current offset to an offset in the remaining region. Initially, the active region is empty. If the current offset advances beyond the chosen offset, the active region will also be empty. /------------entire length---------------\ /----- used region -----\/-- available --\ +----------------------------------------+ | consumed | remaining | | +----------------------------------------+ a b c d e a == base of buffer. b == current pointer. Can be anywhere between a and d. c == active pointer. Meaningful between b and d. d == used pointer. e == length of buffer. a-e == entire length of buffer. a-d == used region. a-b == consumed region. b-d == remaining region. b-c == optional active region. lwres_buffer_init() initializes the lwres_buffer_t *b and assocates it with the memory region of size length bytes starting at location base. lwres_buffer_invalidate() marks the buffer *b as invalid. Invalidating a buffer after use is not required, but makes it possible to catch its possible accidental use. The functions lwres_buffer_add() and lwres_buffer_subtract() respectively increase and decrease the used space in buffer *b by n bytes. lwres_buffer_add() checks for buffer overflow and lwres_buffer_subtract() checks for underflow. These functions do not allocate or deallocate memory. They just change the value of used. A buffer is re-initialised by lwres_buffer_clear(). The function sets used, current and active to zero. lwres_buffer_first makes the consumed region of buffer *p empty by setting current to zero (the start of the buffer). lwres_buffer_forward() increases the consumed region of buffer *b by n bytes, checking for overflow. Similarly, lwres_buffer_back() decreases buffer b's consumed region by n bytes and checks for underflow. lwres_buffer_getuint8() reads an unsigned 8-bit integer from *b and returns it. lwres_buffer_putuint8() writes the unsigned 8-bit integer val to buffer *b. lwres_buffer_getuint16() and lwres_buffer_getuint32() are identical to lwres_buffer_putuint8() except that they respectively read an unsigned 16-bit or 32-bit integer in network byte order from b. Similarly, lwres_buffer_putuint16() and lwres_buffer_putuint32() writes the unsigned 16-bit or 32-bit integer val to buffer b, in network byte order. Arbitrary amounts of data are read or written from a lightweight resolver buffer with lwres_buffer_getmem() and lwres_buffer_putmem() respectively. lwres_buffer_putmem() copies length bytes of memory at base to b. Conversely, lwres_buffer_getmem() copies length bytes of memory from b to base. COPYRIGHT
Copyright (C) 2004, 2005, 2007 Internet Systems Consortium, Inc. ("ISC") Copyright (C) 2000, 2001 Internet Software Consortium. BIND9 Jun 30, 2000 LWRES_BUFFER(3)
All times are GMT -4. The time now is 01:25 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy