public inbox for linux-8086@vger.kernel.org
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: u-vpoa@aetey.se
Cc: Juan Perez-Sanchez <lithoxs@gmail.com>,
	linux-8086 <linux-8086@vger.kernel.org>
Subject: Re: the memory model being used in elks?
Date: Sun, 10 May 2015 21:27:44 +0100	[thread overview]
Message-ID: <20150510212744.60ca87d4@www.etchedpixels.co.uk> (raw)
In-Reply-To: <20150510184027.GN8197@example.net>

On Sun, 10 May 2015 20:40:27 +0200
u-vpoa@aetey.se wrote:

> On Sun, May 10, 2015 at 10:31:38AM -0500, Juan Perez-Sanchez wrote:
> > Compile with flags
> > 
> >  -i -H E000
> > 
> > Flag H controls the size of BSS.
> 
> I see, a minix-like static allocation (I'm guessing this is needed
> because ELKS does not yet handle overlapping segments between different
> processes so it does not want to allocate a whole segment to each process
> per default?).

Classic Unix defines the memory map as

   <--- Data ---><--- BSS ---> | <--- Space ---> | <--- Stack --- >

Where the upper divide is SP and the lower one is set by brk() or sbrk().
The space in the middle doesn't all really exist if you have an MMU with
any kind of sane paging system.

If you have support built for ELKS pattern binaries then you can do
resizing at runtime as they are laid out to allow the bss to extend

Alan

  reply	other threads:[~2015-05-10 20:27 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-08 20:14 the memory model being used in elks? u-vpoa
2015-05-09 17:03 ` One Thousand Gnomes
2015-05-09 17:47   ` u-vpoa
2015-05-09 17:50     ` Jody Bruchon
2015-05-09 18:38       ` u-vpoa
2015-05-10 15:31         ` Juan Perez-Sanchez
2015-05-10 18:40           ` u-vpoa
2015-05-10 20:27             ` Alan Cox [this message]
2015-05-10 21:19               ` u-vpoa
2015-05-10 21:51                 ` Alan Cox
2015-05-11  6:10                   ` u-vpoa
2015-05-11  9:27                     ` Alan Cox
2015-05-11 11:25                       ` u-vpoa

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=20150510212744.60ca87d4@www.etchedpixels.co.uk \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=linux-8086@vger.kernel.org \
    --cc=lithoxs@gmail.com \
    --cc=u-vpoa@aetey.se \
    /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