From: David Presotto <presotto@closedmind.org>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] size on /proc files?
Date: Sun, 30 Mar 2003 07:48:23 -0500 [thread overview]
Message-ID: <58a8262f422a9bc5d33049fcd39ae124@plan9.bell-labs.com> (raw)
In-Reply-To: <091f807138892efebadcbbde9ac80bd7@plan9.bell-labs.com>
Thinking a bit more on it and looking at devproc.c and sysproc.c, the text
size is easy to get right, it's in the text segment. The process is a
bit more problematic since the address space is sparse. The text/data/bss are
at one end (right after an invalid page to catch null regs), the stack at the other,
and other segs anywhere in between. The easy thing would be to say all procs are
0x7ffff000 bytes long. That would help your get_a_record routine but wouldn't
really be very informative. You'ld be better off reading the segment file to see what
is and isn't there than just checking a length of the mem file.
next prev parent reply other threads:[~2003-03-30 12:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-30 10:36 Aharon Robbins
2003-03-30 12:34 ` David Presotto
2003-03-30 12:48 ` David Presotto [this message]
2003-03-30 14:48 ` Russ Cox
2003-03-31 9:08 ` Aharon Robbins
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=58a8262f422a9bc5d33049fcd39ae124@plan9.bell-labs.com \
--to=presotto@closedmind.org \
--cc=9fans@cse.psu.edu \
/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;
as well as URLs for NNTP newsgroup(s).