09-27-2011
The used number in free is the sum of memory used by applications, buffers, and caches, and not only that of the applications. Linux will always try to use as much memory as possible to cache files to reduce disk access (which is a good thing).
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
How do i check/get the total amount of RAM, on a machine running UNIX? (4 Replies)
Discussion started by: samudimu
4 Replies
2. Solaris
Hi All,
I am trying to find the physical memory usage by each process/users.
Can you please let me know how to get the memory usage?.
Thanks,
bsraj. (12 Replies)
Discussion started by: bsrajirs
12 Replies
3. UNIX for Dummies Questions & Answers
I'm writing a shell script to display as much useful information on physical and virtual memory availability and usage as possible. I need a CLI tool to print these numbers for me.
The utilities that I know to give out some statistics are the following:
free
top
vmstat
sysctl
In Linux... (1 Reply)
Discussion started by: fiori_musicali
1 Replies
4. Filesystems, Disks and Memory
A bit of background
I'm running a Nexenta (OpenSolaris kernel + a number of Debian tools) server running a ZRAID of 3x 1TB SATA2 drives (essentially a RAID5 formatted in ZFS, for those who aren't familiar with zpools).
When running the ZFS scrub command (ZFS's equivelent of fsck) I get a number... (0 Replies)
Discussion started by: laumars
0 Replies
5. Solaris
Hi
How to display RAM memory info under Sol10 ?
I need info like :
- how many slots is available in MoBo
- how RAM is plugged into those slots
- total number of RAM memory size and size divided in each slot
ths for help. (2 Replies)
Discussion started by: presul
2 Replies
6. Shell Programming and Scripting
Hi,
I am trying to get the system RAM size from "top" command's output by the following but it is not working.
top | sed "s/^Mem.**\(*\), *//" (10 Replies)
Discussion started by: royalibrahim
10 Replies
7. Solaris
Hi All,
Ram memory always fails,i did not find the reason...........any one can help i this.:wall: (2 Replies)
Discussion started by: Rajesh_Apple
2 Replies
8. Ubuntu
How do I find if I have defective ram in my computer.
I don't have a cd-rom, so I can't use a bootable cd. (1 Reply)
Discussion started by: locoroco
1 Replies
9. Programming
When we dynamically allocate the memory say 100 integers say
int *x = new int(1000);
then does entire chunk of memory gets allocated at once after the completion of the statement?
I mean will the the concept of page fault come into picture over here? (3 Replies)
Discussion started by: rupeshkp728
3 Replies
10. Filesystems, Disks and Memory
Hi,
i have just installed 4 gb RAM ddr3 on OS Windows 7 32 bit.
In "manage peripherals" i see this section:
Memory installed (ram) : 4,00 gb (2,30gb usable)
Why only 2,30 gb usable ?
In Windows 7 32bit the maximum size is not 3,00gb ?
see file attached, please (4 Replies)
Discussion started by: nash83
4 Replies
libcache(3) BSD Library Functions Manual libcache(3)
NAME
libcache -- the caching framework
SYNOPSIS
#include <cache.h>
DESCRIPTION
The libcache framework provides a facility for creating in memory data caches. Each cache is a mutable dictionary that associates values
with their keys. A cache limits the number of values it keeps according to available system memory and selects values to evict when the
limit is exceeded. Recently and frequently used values are less likely to be selected for eviction.
Cache keys and values should be cast as pointers. The framework provides a callback interface for supporting arbitrary types of keys and
values and implements callback functions for common types. See cache_callbacks(3) for more information.
Clients retrieve a value previously added to a cache using the value's key. When the client gets a value, the cache increments a reference
count on the value. When the client finishes with a value retrieved from a cache they must release the value back to the cache. Referenced
values are considered in use and will not be evicted. The cache may evict unreferenced values (e.g. to make room for other values or reduce
its size).
The number of values allowed in a cache at one time is managed by the cache framework. Cache size will grow when the system has available
memory and shrink under memory pressure.
Libcache is thread-safe. It is not safe to call back into the cache API from cache callback functions.
SEE ALSO
cache_create(3), cache_set_and_retain(3)
Darwin May 7, 2009 Darwin