From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Daniel Schnell <daniel.schnell@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] Maximum number of realtime tasks
Date: Tue, 31 Oct 2006 12:54:16 +0100 [thread overview]
Message-ID: <45473968.2070906@domain.hid> (raw)
In-Reply-To: <DD39B5C3F4963040ADC9768BE7E430CB0144D60E@is-hdq-exchange.marel.net>
Daniel Schnell wrote:
> Gilles Chanteperdrix wrote:
>
>>Pay attention to the stack size of the user-space tasks: the default
>>of 8 Megabytes will exhaust your RAM rapidly. So, you should either :
>>- set the default stack size with ulimit;
>>- or set the the stack size of the created threads, but in this case
>>the main thread will have an 8 Megabytes stack.
>>
>>In order to set the stack size of a thread, use
>>pthread_attr_setstacksize if using the POSIX skin or the stksize
>>parameter of rt_task_create if using the native skin.
>
>
> If I set the stacksize generally via ulimit -s and additionally via the
> pthread_attr_setstacksize() how is the precedence of one of these calls
> over the other ? Does pthread_attr_setstacksize
Setting the stack size with pthread_attr_setstacksize seems to allow a
stack greater than the limit fixed by ulimit, but I do not think it is
wise to rely on such a behaviour.
--
Gilles Chanteperdrix
next prev parent reply other threads:[~2006-10-31 11:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-31 8:51 [Xenomai-help] Maximum number of realtime tasks Frits de Klark
2006-10-31 9:04 ` Philippe Gerum
2006-10-31 9:13 ` Gilles Chanteperdrix
2006-10-31 11:38 ` Daniel Schnell
2006-10-31 11:54 ` Gilles Chanteperdrix [this message]
2006-10-31 12:15 ` Daniel Schnell
2006-10-31 15:43 ` Gilles Chanteperdrix
-- strict thread matches above, loose matches on Subject: below --
2006-10-31 11:38 Daniel Schnell
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=45473968.2070906@domain.hid \
--to=gilles.chanteperdrix@xenomai.org \
--cc=daniel.schnell@domain.hid \
--cc=xenomai@xenomai.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.