All of lore.kernel.org
 help / color / mirror / Atom feed
From: Harry Kalogirou <harkal@gmx.net>
To: Dan Olson <dano@agora.rdrop.com>
Cc: Martin Herrman <martin@tuxserver.dyndns.org>,
	Linux-8086 <linux-8086@vger.kernel.org>
Subject: Re: buddy algorithm
Date: 11 Jan 2003 00:37:35 +0200	[thread overview]
Message-ID: <1042238247.1322.48.camel@cool> (raw)
In-Reply-To: <20030110143434.G27221-100000@agora.rdrop.com>


> I was under the impression that ELKS assigns 64k to each process, so a
> single 16 bit data pointer can be used and the different segments can be
> simply divided so that each process owns one.  There are others on the
> list with much more knowledge about this, though, so I'll wait for one of
> them to clear things up.
> 
> 	Dan

ELKS assigns to the process an initial amount of memory for the stack.
From there that memory is grown as the libc instructs with sys_brk()
calls. 

Harry




  reply	other threads:[~2003-01-10 22:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20030110214652Z266323-22911+21374@vger.kernel.org>
2003-01-10 22:16 ` buddy algorithm Martin Herrman
2003-01-10 22:36   ` Dan Olson
2003-01-10 22:37     ` Harry Kalogirou [this message]
2003-01-11  2:41   ` Alan Cox

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=1042238247.1322.48.camel@cool \
    --to=harkal@gmx.net \
    --cc=dano@agora.rdrop.com \
    --cc=linux-8086@vger.kernel.org \
    --cc=martin@tuxserver.dyndns.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.