From: Giacomo Tesio <giacomo@tesio.it>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: [9fans] segbrk(2) vs friends
Date: Mon, 7 Dec 2015 17:00:33 +0100 [thread overview]
Message-ID: <CAHL7psHk67snfhLU-TnhCzr=001PxWSpLqCtn5GCp9jf9M_RkA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 681 bytes --]
I'm trying to understand the reason behind the introduction of segbrk(2).
I cannot find a use case in the codebase.
The manual <http://man.cat-v.org/plan_9/2/segbrk>page states that:
The segbrk system call may go away or
be re-implemented to give more general segment control, sub-
suming the functions of brk(2) <http://man.cat-v.org/plan_9/2/brk>,
segflush(2) <http://man.cat-v.org/plan_9/2/segflush> and segfree
insegattach(2) <http://man.cat-v.org/plan_9/2/segattach>.
But given the manpage itself is pretty cryptic, I wonder if it's outdated.
Or if it is actually deprecated.
Do you know any paper that can explain its design and intent?
Giacomo
[-- Attachment #2: Type: text/html, Size: 920 bytes --]
reply other threads:[~2015-12-07 16:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CAHL7psHk67snfhLU-TnhCzr=001PxWSpLqCtn5GCp9jf9M_RkA@mail.gmail.com' \
--to=giacomo@tesio.it \
--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).