From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: xenomai@xenomai.org
Subject: Re: [Xenomai] [Xenomai-git] Philippe Gerum : cobalt/posix: drop pthread_make_periodic_np/ wait_period_np services
Date: Mon, 16 Jun 2014 21:02:56 +0200 [thread overview]
Message-ID: <539F3F60.5040304@xenomai.org> (raw)
In-Reply-To: <E1WwZye-0002zC-2B@sd-51317.dedibox.fr>
On 06/16/2014 06:41 PM, git repository hosting wrote:
> Module: xenomai-forge
> Branch: next
> Commit: a4a6ff9a9c9614d3e8ac860386fa3b168c649af0
> URL: http://git.xenomai.org/?p=xenomai-forge.git;a=commit;h=a4a6ff9a9c9614d3e8ac860386fa3b168c649af0
>
> Author: Philippe Gerum <rpm@xenomai.org>
> Date: Mon Jun 16 18:39:44 2014 +0200
>
> cobalt/posix: drop pthread_make_periodic_np/wait_period_np services
>
> We have no more in-tree users of these calls.
>
> With the introduction of services to support real-time signals, those
> two non-portable calls have become redundant. Instead, Cobalt-based
> applications should create a periodic timer using the timer_create()
> call, and wait for release points via sigwaitinfo(), checking for
> overruns by looking at the siginfo.si_overrun field.
>
> Alternatively, applications may include a timer source in a
> synchronous multiplexing operation, by passing a file descriptor
> returned by the timerfd() service to a select() call.
Actually, read is more direct than select + read, and it allows to get
the count of overruns too.
--
Gilles.
next parent reply other threads:[~2014-06-16 19:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1WwZye-0002zC-2B@sd-51317.dedibox.fr>
2014-06-16 19:02 ` Gilles Chanteperdrix [this message]
2014-06-16 19:16 ` [Xenomai] [Xenomai-git] Philippe Gerum : cobalt/posix: drop pthread_make_periodic_np/ wait_period_np services Philippe Gerum
2014-06-16 19:36 ` Philippe Gerum
2014-06-16 21:14 ` Gilles Chanteperdrix
2014-06-17 7:23 ` Philippe Gerum
2014-06-17 7:26 ` Gilles Chanteperdrix
2014-06-17 7:36 ` 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=539F3F60.5040304@xenomai.org \
--to=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.