From: Milind <dmilind@india.hp.com>
To: mark@winksmith.com
Cc: linux-kernel@vger.kernel.org, blore-linux@yahoogroups.com
Subject: Re: FW: [ma-linux] Info about top command required
Date: Wed, 08 Aug 2001 11:18:23 +0530 [thread overview]
Message-ID: <3B70D2A6.F0C0ACC4@india.hp.com> (raw)
In-Reply-To: <001f01c11fca$3bfd5ec0$94604c0f@india.hp.com>
Hi mark ,
Thanks for the info.
But the question really is , whether SIZE corrosponds to
real memory( real text + real data + real stack)
OR
virtual memory(virtual text + virtual data + virtual stack)
OR
both????
Thanks
Milind
> -----Original Message-----
> From: mark@winksmith.com [mailto:mark@winksmith.com]
> Sent: Tuesday, August 07, 2001 6:13 PM
> To: Ananth P
> Cc: TUXMA (E-mail)
> Subject: Re: [ma-linux] Info about top command required
>
> On Tue, Aug 07, 2001 at 12:55:28PM +0530, Ananth P wrote:
> > I wanted to know how the 'SIZE' field in the output of 'top' command is
> > calculated in linux.
>
> well, if i remember correctly the size field in ps results in process
> size in clicks. one click is 4096 bytes. it's pretty good for relative
> measurement (e.g. this one is 50 clicks, the other one is 5000 clicks).
>
> let's see about 'top'. reading man page
>
> SIZE The size of the task's code plus data plus stack
> space, in kilobytes, is shown here.
>
> so, it sounds like kb. in addition, you might find these fields helpful
> too (from the man page).
>
> TSIZE The code size of the task. This gives strange
> values for kernel processes and is broken
> for ELF processes.
>
> DSIZE Data + Stack size. This is broken for ELF
> processes.
>
> --
> Mark Smith
> mark@winksmith.com
next parent reply other threads:[~2001-08-08 5:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <001f01c11fca$3bfd5ec0$94604c0f@india.hp.com>
2001-08-08 5:48 ` Milind [this message]
2001-08-08 14:09 ` Info about top command required Milind
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3B70D2A6.F0C0ACC4@india.hp.com \
--to=dmilind@india.hp.com \
--cc=blore-linux@yahoogroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark@winksmith.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox