active memory - ok, but per process ?
Hi,
pardon - a user question, most likely for vm subsystem experts. Im searching for this for a while and dont know any further.....
as we know ,
cat /proc/meminfo |grep Active
Active: 139916
kB
gives the " Memory that has been used more recently and usually not reclaimed unless absolutely necessary."
I wonder - isn`t there a way to break that down on a per-process basis ? (to see which process is the most active memory "consumer")
regards
Roland
___________________________________________________________
Neu: WEB.DE De-Mail - Einfach wie E-Mail, sicher wie ein Brief! Jetzt De-Mail-Adresse reservieren: https://produkte.web.de/go/demail02
I'm not a vm subsystem experts, but maybe I can give my own comments. Actually it's hard to maintenance per-process active pages. active pages include many file page caches, not only per-process pages, these caches don't belong to any process.(like some share library code page).
So apparantly there have many common active mm through all process. is this active mm number useful for you?
Maybe you can take some useful number like RSS & VSZ .(ps aux)
Quoted 26 lines · On Tue, Sep 14, 2010 at 5:29 AM, <[email protected]> wrote:
Hi,
pardon - a user question, most likely for vm subsystem experts. I
m searching for this for a while and dont know any further.....as we know ,
cat
/proc/meminfo|grep Active
Active: 139916
kBgives the " Memory that has been used more recently and usually not reclaimed unless absolutely necessary."
I wonder - isn`t there a way to break that down on a per-process basis ? (to see which process is the most active memory "consumer")
regards
Roland
___________________________________________________________
Neu: WEB.DE De-Mail - Einfach wie E-Mail, sicher wie ein Brief! Jetzt De-Mail-Adresse reservieren: https://produkte.web.de/go/demail02
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/