All of lore.kernel.org
 help / color / mirror / Atom feed
From: Harry Kalogirou <harkal@gmx.net>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Ken Martwick <kenm@efn.org>, Linux-8086 <linux-8086@vger.kernel.org>
Subject: Re: Small-C revisited
Date: 05 Jun 2002 23:52:40 +0300	[thread overview]
Message-ID: <1023309881.2364.16.camel@cool> (raw)
In-Reply-To: <1023298079.2442.6.camel@irongate.swansea.linux.org.uk>

Την Τετ, 05-06-2002 στις 20:27, ο/η Alan Cox έγραψε:
 
> Our current binary format is the minix one and has the same design flaw.
> Minix doesn't support swapping so allocates a program data as
> 
> 		Data
> 		<space>
> 		Stack
> 
> And brk()/malloc etc expand into pre-reserved space. Chmem adjusts that
> space. What probably should happen since we do have swap is that we
> allocate
> 
> 		Stack (size configured at compile/link time)
> 		Data
> 
> We can then actually expand the program space if need be. On v7 swap is
> activated at boot up and they basically did
> 
> 		if(room to just grow a bit)
> 			grow_it()
> 		else
> 			swap_it_out()
> 
> and the swap back in would sort out a suitable sized chunk.
> 

That is what I was planning to implement next. I'm currently working on
making an efficient memory defrager but I got bored when the ELKS tree
got uncompilable.

Harry



-
To unsubscribe from this list: send the line "unsubscribe linux-8086" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2002-06-05 20:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-05  3:23 Small-C revisited Ken Martwick
2002-06-05  7:00 ` Riley Williams
2002-06-05 17:27 ` Alan Cox
2002-06-05 20:52   ` Harry Kalogirou [this message]
2002-06-05 17:31 ` Alan Cox
2002-06-05 18:56   ` Manuel Novoa III

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=1023309881.2364.16.camel@cool \
    --to=harkal@gmx.net \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=kenm@efn.org \
    --cc=linux-8086@vger.kernel.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.