search

mfrw / compcache

Automatically exported from code.google.com/p/compcache
0 stars 0 forks source link

Memory consumption not documented #52

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Nowhere in the program documentation is there text explaining to the end-
taken outright and marked as used kernel memory (it certainly does not
appear as a separate app in the process list)?  How can this be known using
a program like free or top?  What effects can the end-user witness when
loading / initializing / running compcache to verify empirically that it is
working?

Original issue reported on code.google.com by dragonf...@gmail.com on 11 Jan 2010 at 11:41

GoogleCodeExporter commented 9 years ago 
You can get ramzswap stats using the rzscontrol utility included with the 
download
package.

rzscontrol /dev/ramzswap0 --stats

(see rzscontrol manpage for more details:
http://compcache.googlecode.com/hg/sub-projects/rzscontrol/man/rzscontrol.html)

'MemUsedTotal' field shows amount of memory used by given device.

Documentation for all stats is present at:
http://code.google.com/p/compcache/wiki/StatsExplained
(note that we no longer create /proc/ramzswap node).

Original comment by nitingupta910@gmail.com on 11 Jan 2010 at 1:31

GoogleCodeExporter commented 9 years ago 
Yeah but that does not tell the user what effects ramzswap has in top and in 
free.

Original comment by dragonf...@gmail.com on 11 Jan 2010 at 5:32

GoogleCodeExporter commented 9 years ago 
> Yeah but that does not tell the user what effects ramzswap has in top and in 
free.

top/free shows swap usage. This swap usage is obviously not equal to memory 
consumed
by ramzswap device, as explained with StatsExplained page.

I have no plans to integrate stats, as exported by rzscontrol, with top/free.

Original comment by nitingupta910@gmail.com on 12 Jan 2010 at 1:14

GoogleCodeExporter commented 9 years ago

Original comment by nitingupta910@gmail.com on 18 Jan 2010 at 10:47