From: Jody Bruchon <jody@jodybruchon.com>
To: ELKS <linux-8086@vger.kernel.org>
Subject: Re: the memory model being used in elks?
Date: Sat, 09 May 2015 13:50:44 -0400 [thread overview]
Message-ID: <554E48F4.5010406@jodybruchon.com> (raw)
In-Reply-To: <20150509174703.GK8197@example.net>
On 5/9/2015 1:47 PM, u-vpoa@aetey.se wrote:
> IOW, as much as I can see, the binary is built correctly and it is
> the memory allocation by the kernel which looks surprizing.
It is my understanding that bcc assumes DS=ES=SS and both stack and heap
data use the same code segment. How did you determine the memory usage
of the program to be 60K? Does that include all usage or only heap usage?
next prev parent reply other threads:[~2015-05-09 17:50 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 [this message]
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=554E48F4.5010406@jodybruchon.com \
--to=jody@jodybruchon.com \
--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