All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ignacio García Pérez" <iggarpe@domain.hid>
To: Philippe Gerum <rpm@xenomai.org>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] timeout in native API calls (cond, sem, mutex, etc).
Date: Fri, 21 Oct 2005 20:55:48 +0200	[thread overview]
Message-ID: <435939B4.3090102@domain.hid> (raw)
In-Reply-To: <435919C8.6080906@domain.hid>


>
> The real issue is only about extending the absolute timeout support to
> _all_ blocking primitives from the native API, or only to a single one
> for which there exists a clear POSIX counterpart (i.e. rt_cond_wait ->
> pthread_cond_timedwait). I'd like we focus on this issue instead. IOW,
> would rt_sem_p_abs() or rt_queue_recv_abs() be of any use?

Don't think so. Just liked the idea of an "orthogonal" API. Sometimes
it's simply easier to remember that wherever you specify a timeout you
can do it abs/rel than to remember that some sync primitives allow abs
and other don't.

Nacho.



  reply	other threads:[~2005-10-21 18:55 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-20 16:20 [Xenomai-help] timeout in native API calls (cond, sem, mutex, etc) Ignacio García Pérez
2005-10-20 16:46 ` Jan Kiszka
2005-10-20 17:09   ` Ignacio García Pérez
2005-10-20 17:33     ` Jan Kiszka
2005-10-20 18:18       ` Philippe Gerum
2005-10-20 18:16     ` Philippe Gerum
2005-10-21  7:20       ` Ignacio García Pérez
2005-10-21 10:29         ` Philippe Gerum
2005-10-21 12:02           ` Ignacio García Pérez
2005-10-21 10:51         ` Ignacio García Pérez
2005-10-21 12:23           ` Jan Kiszka
2005-10-21 14:46             ` Ignacio García Pérez
2005-10-21 16:45             ` Philippe Gerum
2005-10-21 16:39           ` Philippe Gerum
2005-10-21 18:55             ` Ignacio García Pérez [this message]
2005-10-21 10:52         ` Ignacio García Pérez
2005-10-21 12:16           ` Jan Kiszka
2005-10-21 14:40             ` Ignacio García Pérez
2005-10-21 16:42           ` 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=435939B4.3090102@domain.hid \
    --to=iggarpe@domain.hid \
    --cc=rpm@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.