public inbox for linux-8086@vger.kernel.org
 help / color / mirror / Atom feed
From: u-vpoa@aetey.se
To: Juan Perez-Sanchez <lithoxs@gmail.com>
Cc: linux-8086 <linux-8086@vger.kernel.org>
Subject: Re: the memory model being used in elks?
Date: Sun, 10 May 2015 20:40:27 +0200	[thread overview]
Message-ID: <20150510184027.GN8197@example.net> (raw)
In-Reply-To: <CAD6VGuanmBim0VXuCXumpp3+aA8TrL4Wibc1rLA=WxbbHFbUtg@mail.gmail.com>

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?).

Yes, indeed, this helped, but I had to both set

 -H0xff00
and
 -DBLON=3584    (reduce the compression block size)

to get rid of "no memory".

The utility still performs better than ELKS compress
but this scaling down should not be needed.

8KB compression block size works under elksemu
(about 9KB extra for the buffers compared to the 3.5KB block),
what causes this difference?

Rl


  reply	other threads:[~2015-05-10 18:40 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 [this message]
2015-05-10 20:27             ` Alan Cox
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=20150510184027.GN8197@example.net \
    --to=u-vpoa@aetey.se \
    --cc=linux-8086@vger.kernel.org \
    --cc=lithoxs@gmail.com \
    /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