9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Charles Forsyth <forsyth@terzarima.net>
To: lucio@proxima.alt.za, 9fans@9fans.net
Subject: Re: [9fans] segfree() - more details?
Date: Thu,  2 Apr 2009 11:31:12 +0100	[thread overview]
Message-ID: <d8e5a489a2445a251fc0acdfe8097c48@terzarima.net> (raw)
In-Reply-To: <6c529a9785a1131ce815f5fa79593321@proxima.alt.za>

>in segattach(2) suggests that there is some mechanism to associate
>disk file portions with memory segments (that being what Unix's MMAP
>does, roughly),

not really: it will read initial text and data from an image,
but that's it.  apparently if you segfree your data space it
will reinitialise it from the image, effectively resetting it,
but i'd be surprised if anything uses that.



  reply	other threads:[~2009-04-02 10:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-02  9:13 lucio
2009-04-02 10:31 ` Charles Forsyth [this message]
2009-04-02 12:50 ` cinap_lenrek
     [not found] <28ec308e3a4db01f0e6367ecb615903b@terzarima.net>
2009-04-02 10:27 ` lucio
2009-04-02 11:44   ` Charles Forsyth
2009-04-02 15:48     ` ron minnich
2009-04-02 17:48       ` lucio

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=d8e5a489a2445a251fc0acdfe8097c48@terzarima.net \
    --to=forsyth@terzarima.net \
    --cc=9fans@9fans.net \
    --cc=lucio@proxima.alt.za \
    /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).