All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@domain.hid>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: xenomai-core <xenomai@xenomai.org>
Subject: Re: [Xenomai-core] XENO_OPT_SYS_STACKPOOLSZ vs. switchtest
Date: Thu, 19 Feb 2009 14:33:56 +0100	[thread overview]
Message-ID: <499D5FC4.4030303@domain.hid> (raw)
In-Reply-To: <499D5B0A.7020608@domain.hid>

Gilles Chanteperdrix wrote:
> Jan Kiszka wrote:
>> Gilles Chanteperdrix wrote:
>>> Jan Kiszka wrote:
>>>> Hi Gilles,
>>>>
>>>> how much XENO_OPT_SYS_STACKPOOLSZ do I need to run switchtest for
>>>> default settings? At least on x86-64, the default 32K is not enough.
>>>> Unless we talk about GB ;), maybe it makes sense to adjust the default
>>>> size accordingly.
>>> It depends on the arguments you pass to switchtest.
>> None, ie. the default settings.
> 
> Then 6 kernel-space tasks are created. Since switchtest is not the

6*4 is 20k... Ah, the well-known allocator overhead, I guess. Will try
with >= 40k.

> average use of Xenomai, and is supposed to be used only for validating
> the context/FPU switches, I would not change XENO_OPT_SYS_STACKPOOL_SZ,
> maybe only add a clear message when creation of kernel-space tasks fails.

Well, isn't the switchtest part of xeno-test? Would be unfortunate to
require a kernel rebuild just for running the standard tests. I think we
don't loose much by slightly increasing the stack to, say, 64K on 32 bit
and 128K on 64 bit archs.

BTW, XNARCH_THREAD_STACKSZ for x86-64 equals the x86-32 bit value (4K)
while I don't think the have they same demands (nor the same resource
restrictions).

Jan

-- 
Siemens AG, Corporate Technology, CT SE 2
Corporate Competence Center Embedded Linux


  reply	other threads:[~2009-02-19 13:33 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-19 10:34 [Xenomai-core] XENO_OPT_SYS_STACKPOOLSZ vs. switchtest Jan Kiszka
2009-02-19 10:44 ` Gilles Chanteperdrix
2009-02-19 11:17   ` Jan Kiszka
2009-02-19 13:13     ` Gilles Chanteperdrix
2009-02-19 13:33       ` Jan Kiszka [this message]
2009-02-19 13:46         ` Gilles Chanteperdrix
2009-02-19 14:13           ` Jan Kiszka
2009-02-19 14:07         ` Philippe Gerum
2009-02-19 14:11           ` Jan Kiszka
2009-02-19 14:42             ` Gilles Chanteperdrix
2009-02-19 15:46               ` Jan Kiszka
2009-02-19 15:11             ` Philippe Gerum
2009-02-19 15:53               ` Jan Kiszka
2009-02-19 16:07                 ` Philippe Gerum

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=499D5FC4.4030303@domain.hid \
    --to=jan.kiszka@domain.hid \
    --cc=gilles.chanteperdrix@xenomai.org \
    --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.