From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 Date: Mon, 7 Dec 2015 17:00:33 +0100 Message-ID: From: Giacomo Tesio To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary=001a114b10520bc1d6052650f5fa Subject: [9fans] segbrk(2) vs friends Topicbox-Message-UUID: 7a5d369c-ead9-11e9-9d60-3106f5b1d025 --001a114b10520bc1d6052650f5fa Content-Type: text/plain; charset=UTF-8 I'm trying to understand the reason behind the introduction of segbrk(2). I cannot find a use case in the codebase. The manual 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) , segflush(2) and segfree insegattach(2) . 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 --001a114b10520bc1d6052650f5fa Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
I'm trying to understand the reason beh= ind the introduction of segbrk(2).

I cannot find a= use case in the codebase.

The manual 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=
), segflush(2) a=
nd segfree in
segattach(2).
=

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
--001a114b10520bc1d6052650f5fa--