OpenVZ Forum


Home » Mailing lists » Devel » How Inactive may be much greather than cached?
How Inactive may be much greather than cached? [message #21948] Thu, 18 October 2007 06:24 Go to previous message
vaverin is currently offline  vaverin
Messages: 708
Registered: September 2005
Senior Member
Hi all,

could anybody explain how "inactive" may be much greater than "cached"?
stress test (http://weather.ou.edu/~apw/projects/stress/) that writes into
removed files in cycle puts the node to the following state:

MemTotal: 16401648 kB
MemFree: 636644 kB
Buffers: 1122556 kB
Cached: 362880 kB
SwapCached: 700 kB
Active: 1604180 kB
Inactive: 13609828 kB

At the first glance memory should be freed on file closing, nobody refers to
file and ext3_delete_inode() truncates inode. We can see that memory is go away
from "cached", however could somebody explain why it become "invalid" instead be
freed? Who holds the references to these pages?

thank you,
	Vasily Averin
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: [PATCH] Fix again the fl6_sock_lookup() fixed locking
Next Topic: [PATCH 0/4] Fix race between sk_filter reassign and sk_clone()
Goto Forum:
  


Current Time: Mon Mar 04 21:52:01 GMT 2024

Total time taken to generate the page: 0.02062 seconds