• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1386
  • Last Modified:

procinfo.h under AIX

The structs procinfo{} and userinfo{} in /usr/include/procinfo.h are containers for quite a bit of information about the processes running on your system. One of my favourite apps, 'monitor' uses them, but I still have problems interpreting all of the elements:

struct      userinfo
      unsigned long      ui_tsize;      /* size of text */
      /* memory usage info */
      unsigned long      ui_drss;      /* data resident set size */
      unsigned long      ui_trss;      /* text resident set size */
      unsigned long      ui_dvm;            /* data virtual memory size */

are dealing with memory sizes, but what sizes are these exactly? What is considered to be 'text', 'data'? Please no guesses, please no easy explanations for beginners, what I need is a good definition of these terms.

Thanks for your input
1 Solution
'text' is the program code itself, while 'data' is the entire data
area (all globals and the malloc'd stuff)). Some (most?) of it
can be swapped out; the resident portion of both the text
and data areas are called the 'working set' of the process.
If I'm not mistaken (no docs here at the moment), all sizes are measured in pages (see man entry for getpagesize()).

kind regards,

Jos aka jos@and.nl
griesshAuthor Commented:
Thanks for the VERY FAST reply!
1) ui_tsize is in byte, everything else in 4K pages!
2) Your explanation makes sense, even if the numbers don't add up
   exactly (I guess there is some process header stuff included).
3) Do you know a good (technical) source for that stuff (There
   are so many other open questions)? IBM's Technical Library
   isn't that much helpful.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now