* Re: FW: [ma-linux] Info about top command required
[not found] <001f01c11fca$3bfd5ec0$94604c0f@india.hp.com>
@ 2001-08-08 5:48 ` Milind
2001-08-08 14:09 ` Milind
0 siblings, 1 reply; 2+ messages in thread
From: Milind @ 2001-08-08 5:48 UTC (permalink / raw)
To: mark; +Cc: linux-kernel, blore-linux
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
^ permalink raw reply [flat|nested] 2+ messages in thread
* Info about top command required
2001-08-08 5:48 ` FW: [ma-linux] Info about top command required Milind
@ 2001-08-08 14:09 ` Milind
0 siblings, 0 replies; 2+ messages in thread
From: Milind @ 2001-08-08 14:09 UTC (permalink / raw)
To: mark; +Cc: linux-kernel, blore-linux
Milind wrote:
> 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
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2001-08-08 14:35 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <001f01c11fca$3bfd5ec0$94604c0f@india.hp.com>
2001-08-08 5:48 ` FW: [ma-linux] Info about top command required Milind
2001-08-08 14:09 ` Milind
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox