aboutsummaryrefslogtreecommitdiff
path: root/share/doc/papers/malloc
diff options
context:
space:
mode:
authorWolfram Schneider <wosch@FreeBSD.org>1996-10-05 18:37:31 +0000
committerWolfram Schneider <wosch@FreeBSD.org>1996-10-05 18:37:31 +0000
commite627b39baccd1ec9129690167cf5e6d860509655 (patch)
treef841fa3fdbb61395df1bed9d54fbb3b4ee7a5fa2 /share/doc/papers/malloc
parenta42830afaaa709a20015b1d233330d11034af5f0 (diff)
Notes
Diffstat (limited to 'share/doc/papers/malloc')
-rw-r--r--share/doc/papers/malloc/kernel.ms4
1 files changed, 2 insertions, 2 deletions
diff --git a/share/doc/papers/malloc/kernel.ms b/share/doc/papers/malloc/kernel.ms
index 1a4e96779368..21dff8d2f43c 100644
--- a/share/doc/papers/malloc/kernel.ms
+++ b/share/doc/papers/malloc/kernel.ms
@@ -6,7 +6,7 @@
.\" this stuff is worth it, you can buy me a beer in return. Poul-Henning Kamp
.\" ----------------------------------------------------------------------------
.\"
-.\" $Id$
+.\" $Id: kernel.ms,v 1.1 1996/04/13 08:30:16 phk Exp $
.\"
.ds RH The kernel and memory
.NH
@@ -30,7 +30,7 @@ for the data and bss section combined and one for the stack.
On some systems the text shared a segment with the data and bss, and was
consequently just as writable as them.
.PP
-In this setup all the the brk(2) system call have to do is to find the
+In this setup all the brk(2) system call have to do is to find the
right amount of free storage, possibly moving things around in physical
memory, maybe even swapping out a segment or two to make space,
and change the upper limit on the data segment according to the address given.