All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Jakub Nowacki <j.s.nowacki@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] Stack size of created task
Date: Wed, 13 Jul 2011 13:43:57 +0200	[thread overview]
Message-ID: <4E1D84FD.7050307@domain.hid> (raw)
In-Reply-To: <4E1D8389.7050305@domain.hid>

On 07/13/2011 01:37 PM, Jakub Nowacki wrote:
> Hi,
> 
> I had a slight problem with freezing tasks in RTXI using Xenomai. 
> Namely, task was working normally for some time and then froze, but just 
> RTXI/task not the whole system. I've found that it was caused by the 
> stack size of a task set to 2000B during the creation. Changing it to 0, 
> i.e., automatic stack size fixed the freezing. My question is what is a 
> preferred value there? Before on the list I asked about a problem with 
> the stack size in the kernel being to small for switchtest to run 
> properly on i7 machine. There, one of the answers was that safe bet is 
> 8kB for 64-bit machine. I'm not sure should I leave the stack size in 
> rt_task_create to 0 or to some high value or it should be machine 
> dependent? What is being put on this stack and how to determine it's 
> size depending on the complexity of the task (number of vars?)?

The stack size of a task is highly dependent on what the task does, and
a little bit less on the architecture. There is no generic answer.

The problem with switchtest was not the task size, but the number of
kernel stacks which were available in the kernel threads stacks pool.
That is an entirely different issue.

-- 
                                                                Gilles.


  reply	other threads:[~2011-07-13 11:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-13 11:37 [Xenomai-help] Stack size of created task Jakub Nowacki
2011-07-13 11:43 ` Gilles Chanteperdrix [this message]
2011-07-13 13:13   ` Jakub Nowacki
2011-07-13 18:04     ` Gilles Chanteperdrix

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=4E1D84FD.7050307@domain.hid \
    --to=gilles.chanteperdrix@xenomai.org \
    --cc=j.s.nowacki@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.