From: u-vpoa@aetey.se
To: ELKS <linux-8086@vger.kernel.org>
Subject: the memory model being used in elks?
Date: Fri, 8 May 2015 22:14:34 +0200 [thread overview]
Message-ID: <20150508201433.GJ8197@example.net> (raw)
Hello,
Finally I tried to test the "pres" utility on elks
as opposed to elksemu.
Too bad, it reports lack of memory
and it looks like the maximum available memory is around 30K,
the console shows:
sys_brk failed: len -32634 > end_seg 30864
sys_brk failed: len -32632 > end_seg 30864
sys_brk failed: len 31368 > end_seg 30864
...
I assumed somehow a data segment with around 60K available,
is this not the case?
The same binary works just fine under elksemu.
Rl
next reply other threads:[~2015-05-08 20:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-08 20:14 u-vpoa [this message]
2015-05-09 17:03 ` the memory model being used in elks? 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
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=20150508201433.GJ8197@example.net \
--to=u-vpoa@aetey.se \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).