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
      Werner
LVL 11
griesshAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

jos010697Commented:
'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
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
griesshAuthor Commented:
jos
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.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
System Programming

From novice to tech pro — start learning today.