public inbox for ecos-patches@sourceware.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugs.ecos.sourceware.org
To: ecos-patches@ecos.sourceware.org
Subject: [Bug 1001344] Allow nc_test_slave for lwIP to compile for targets with 128KiB RAM.
Date: Wed, 16 May 2012 00:28:00 -0000	[thread overview]
Message-ID: <20120516002827.AB7163770003@mail.ecoscentric.com> (raw)
In-Reply-To: <bug-1001344-104@http.bugs.ecos.sourceware.org/>

Please do not reply to this email. Use the web interface provided at:
http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001344

Jonathan Larmour <jifl@ecoscentric.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jifl@ecoscentric.com

--- Comment #20 from Jonathan Larmour <jifl@ecoscentric.com> 2012-05-16 01:28:19 BST ---
First, as per bug 1001586 (specifically:
http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001586#c5 ), I would have
thought the buffer sizes could be smaller: 10240+16+maybe a little more just in
case.

As for the general idea with this patch, I think it is unwise to use fixed
constant sizes for stacks. It's doomed, especially once you involve other, more
stack hungry, architectures than ARM or Cortex.

To get smaller stacks I would suggest starting from
CYGNUM_HAL_STACK_SIZE_MINIMUM, and adding on some numbers of multiples of
CYGNUM_HAL_STACK_FRAME_SIZE plus an extra constant to roughly cover the stack
local variables in the call frame you think you are likely to get, and then add
some more for safety. You can do it so that the numbers you get come out as the
fixed constants you've already determined work for you on the Kinetis, but it
at least means it's more likely to continue to work on other targets. You may
find CYGFUN_KERNEL_THREADS_STACK_MEASUREMENT useful to better inform your
decisions.

Alternatively start from CYGNUM_HAL_STACK_SIZE_TYPICAL and reduce it, but I
think that's a bit riskier, as there's no fixed idea of what is typical, in a
way that makes it easy to reduce.

But I wouldn't just say e.g. "4096", because that's never going to be portable
- for some targets it's excessive, for others it may be too small. The problems
you are seeing with the synth target are probably a symptom of this.

Jifl

-- 
Configure bugmail: http://bugs.ecos.sourceware.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

  parent reply	other threads:[~2012-05-16  0:28 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-26  7:28 [Bug 1001344] New: " bugzilla-daemon
2011-09-26 20:11 ` [Bug 1001344] " bugzilla-daemon
2011-09-26 21:30 ` bugzilla-daemon
2011-09-27  5:45 ` bugzilla-daemon
2011-09-27  7:35 ` bugzilla-daemon
2011-09-27  9:06 ` bugzilla-daemon
2011-10-02 14:36 ` bugzilla-daemon
2011-10-02 17:23 ` bugzilla-daemon
2011-10-02 17:29 ` bugzilla-daemon
2011-10-02 17:32 ` bugzilla-daemon
2011-10-02 17:36 ` bugzilla-daemon
2011-10-02 17:50 ` bugzilla-daemon
2011-10-02 19:06 ` bugzilla-daemon
2011-10-02 19:24 ` bugzilla-daemon
2012-05-13 10:50 ` bugzilla-daemon
2012-05-13 11:22 ` bugzilla-daemon
2012-05-14 20:36 ` bugzilla-daemon
2012-05-15  9:26 ` bugzilla-daemon
2012-05-15  9:55 ` bugzilla-daemon
2012-05-15 11:04 ` bugzilla-daemon
2012-05-16  0:28 ` bugzilla-daemon [this message]
2012-05-16 16:04 ` bugzilla-daemon
2012-05-16 16:20 ` bugzilla-daemon
2012-05-17 15:54 ` bugzilla-daemon
2012-05-17 16:12 ` bugzilla-daemon
2012-05-17 16:12 ` bugzilla-daemon
2012-05-17 17:04 ` bugzilla-daemon
2012-05-17 17:45 ` bugzilla-daemon
2012-05-18  7:25 ` bugzilla-daemon
2012-05-18 15:28 ` bugzilla-daemon
2012-05-26 19:19 ` bugzilla-daemon
2012-05-27  0:09 ` bugzilla-daemon
2012-05-27  8:32 ` bugzilla-daemon

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=20120516002827.AB7163770003@mail.ecoscentric.com \
    --to=bugzilla-daemon@bugs.ecos.sourceware.org \
    --cc=ecos-patches@ecos.sourceware.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).