From: Philippe Gerum <rpm@xenomai.org>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Xenomai <xenomai@xenomai.org>
Subject: Re: Moving inband work off stack - remaing cases
Date: Fri, 11 Jun 2021 17:35:32 +0200 [thread overview]
Message-ID: <875yykbeij.fsf@xenomai.org> (raw)
In-Reply-To: <f5a5c0eb-444d-2af3-b493-ec0c9b9ee428@siemens.com>
Jan Kiszka <jan.kiszka@siemens.com> writes:
> Hi Philippe,
>
> I'm trying to understand the reasoning for moving inband work struct for
> the remaining cases of the triggering stack.
>
> To my understanding, this is not needed for xnthread_map (to be
> privatized soon, so only for the in-tree case) because the caller
> providing the struct waits for the completion which will be triggered
> via the inband handler.
>
Correct.
> Looking at xnthread_relax(), the same should apply to post_wakeup -
> provided it is inlined into xnthread_relax - because, again, we won't
> leave that function before the signal was sent, thus the work consumed.
>
Correct.
> Am I missing something?
>
Nope.
--
Philippe.
next prev parent reply other threads:[~2021-06-11 15:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-11 11:21 Moving inband work off stack - remaing cases Jan Kiszka
2021-06-11 15:35 ` Philippe Gerum [this message]
2021-06-11 16:19 ` Jan Kiszka
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=875yykbeij.fsf@xenomai.org \
--to=rpm@xenomai.org \
--cc=jan.kiszka@siemens.com \
--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.