dmesg query

[khilari]

Can someone kindly elaborate on the different parameters of memeory information.
Thanks
Memory Information:
physical page size = 4096 bytes,
logical page size = 4096 bytes
Physical: 3932136 Kbytes,
lockable: 3013432 Kbytes,
available: 3462904 Kbytes

[Don Morris_1]

Ok...

physical page size = 4096 bytes ==> This system is using 4kb as the basic page size [no system page will represent less than 4kb, and the page based metadata in the kernel will be based off of 4kb.

logical page size = 4096 bytes ==> Not surprisingly, the kernel is using 4kb translations as the smallest size to match the 4kb physical pages. This will be the result of sysconf(_SC_PAGE_SIZE) at runtime, and matters for mprotect boundaries, new mapping alignments, etc.]. Note that larger logical pages (i.e. Large Page Translations) are still possible -- this is the lowest page size, not the only one.

Physical: 3932136 Kbytes ==> The kernel sees 3932136 kb of RAM during this boot as available to it (this should be your system memory minus pages stolen by Firmware, bad pages, or other memory hiding mechanisms). That's 3839.9765625Mb or around 3.75Gb if you didn't want to do the math yourself.

lockable: 3013432 Kbytes ==> Of that 3.75Gb, the kernel will allow around 2.873 Gb of it to be locked [locked pages are exempt from vhand paging them out]. Kernel pages are *always* lockable. User pages can be locked via the mlock/plock/mlockall interfaces with sufficient permission. Man on those interfaces, read the VM white paper,
http://docs.hp.com/en/B2355-60103/unlockable_mem.5.html (obsoleted on 11.31).

available: 3462904 Kbytes ==> Of that 3.75Gb, at this point in boot 3.30 Gb is available [i.e. the kernel consumed about .45 Gb bringing up the system and making the metadata it needs to manage things]. Early Boot allocations tend to be the longest-lasting of all kernel allocations (since they tend to be for root metadata that doesn't get resized or freed), so you can assume this is the most memory you'll ever have without a reboot.

Did that help?

[tsf_1]

http://www.docs.hp.com/en/1218/mem_mgt.html

HP-UX Memory Management(White Paper)

will have all answers you want!