ProgrammingThis forum is for all programming questions.
The question does not have to be directly related to Linux and any language is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Unfortunately, there's usually not a decent way to get that info through a clean API. The proc filesystem is there in part because of that shortcoming. If you take a look at the ps and top tools source you'll see that usually they just read the info out of a node somewhere under /proc and parse it. If you don't feel at all like learning about the format, there is the libgtop library from Gnome, http://www.gnome.org/softwaremap/projects/libgtop/. It's just a library that does that parsing for you. -- Rev
The memory info is in /proc/meminfo. There's an entry under /proc for each running process (and under Linux processes and threads are pretty much the same thing, a 'thread' is just a process which shares it's memory space with another process) that has more specific info. Sounds like most of the info you want is in /proc/$PID/status or from the directory /proc/$PID/fd. I believe you'll have to walk the process tree in order to figure out how many threads a process has created, and I'm not sure how to aggregate the processes into thread groups, although I assume the Tgid has something to do with it. I've never used libgtop, so I can't tell you what calls to use there. You'll have to check the docs or find some examples. Maybe someone who has used gtop will be kind enough to post a simple snippet. -- Rev
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.