From: Philippe Gerum <rpm@xenomai.org>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Xenomai <xenomai@xenomai.org>
Subject: Re: "rtdm/nrtsig: move inband work description off the stack"
Date: Tue, 25 May 2021 10:46:19 +0200 [thread overview]
Message-ID: <87lf83cj7k.fsf@xenomai.org> (raw)
In-Reply-To: <2098c9e4-4fb1-ef49-2c2d-d2c6573499b5@siemens.com>
Jan Kiszka <jan.kiszka@siemens.com> writes:
> Hi Philippe,
>
> [1] makes rtdm_schedule_nrt_work a rather heavyweight service, compared
> to what it was (and even over I-pipe). xnmalloc is nothing you would
> expect from a "send a signal" service, specifically from
> rtdm_nrtsig_pend which does not even make use of the sending extra payload.
>
> Can we do better? Also for xnthread_signal (fd and udd usecases are not
> time-sensitive anyway).
>
Nope, I cannot see any significantly better option which would still
allow a common implementation we can map on top of Dovetail / I-pipe.
--
Philippe.
next prev parent reply other threads:[~2021-05-25 8:46 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-25 7:35 "rtdm/nrtsig: move inband work description off the stack" Jan Kiszka
2021-05-25 8:46 ` Philippe Gerum [this message]
2021-05-25 8:58 ` Jan Kiszka
2021-05-25 10:01 ` Philippe Gerum
2021-05-25 10:38 ` Jan Kiszka
2021-05-25 12:37 ` Philippe Gerum
2021-05-25 12:56 ` Jan Kiszka
2021-05-25 13:20 ` Philippe Gerum
2021-05-25 17:08 ` Jan Kiszka
2021-05-26 13:52 ` Philippe Gerum
2021-05-31 15:07 ` Jan Kiszka
2021-06-02 6:51 ` Philippe Gerum
2021-06-04 6:34 ` Chen, Hongzhan
2021-06-04 7:34 ` Jan Kiszka
2021-06-04 7:51 ` Philippe Gerum
2021-06-04 7:54 ` Jan Kiszka
2021-06-04 8:15 ` Philippe Gerum
2021-06-04 8:21 ` Jan Kiszka
2021-06-04 12:53 ` Philippe Gerum
2021-06-04 8:36 ` Chen, Hongzhan
2021-06-04 12:54 ` 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=87lf83cj7k.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.