From: lucio@proxima.alt.za
To: 9fans@9fans.net
Subject: Re: [9fans] segfree() - more details?
Date: Thu, 2 Apr 2009 19:48:18 +0200 [thread overview]
Message-ID: <b884a061f3d419f0f541c4319e251fe6@proxima.alt.za> (raw)
In-Reply-To: <13426df10904020848h28da0b50lb1219561cde88c27@mail.gmail.com>
> see port/fault.c to see what happens on a page fault in the text segment.
Yep, I remember trying to understand that part from a rather
superficial study of the sources. Nemo's commentary will no doubt
prove itself invaluable once again, as soon as I track it down (time
to print a copy). And thanks to Cinap for his comments, as usual very
much to the point.
Why I find all this so confusing after long years in the business
beats me. Must be old age. I guess I should be grateful it's not
Linux I am trying to make sense of.
++L
next prev parent reply other threads:[~2009-04-02 17:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 [this message]
2009-04-02 9:13 lucio
2009-04-02 10:31 ` Charles Forsyth
2009-04-02 12:50 ` cinap_lenrek
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=b884a061f3d419f0f541c4319e251fe6@proxima.alt.za \
--to=lucio@proxima.alt.za \
--cc=9fans@9fans.net \
/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).