From: Wolfgang Mauerer <wm@domain.hid>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: Jan Kiszka <jan.kiszka@domain.hid>,
"xenomai@xenomai.org" <xenomai@xenomai.org>
Subject: Re: [Xenomai-core] Realtime gettimeofday()
Date: Thu, 03 Dec 2009 21:31:25 +0100 [thread overview]
Message-ID: <4B18201D.30003@domain.hid> (raw)
In-Reply-To: <4B17BF4E.7080509@domain.hid>
Gilles Chanteperdrix wrote:
> Wolfgang Mauerer wrote:
>> Hi,
>>
>> On 03.12.2009, at 14:14, Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org
>> > wrote:
>>
>>> Wolfgang Mauerer wrote:
>>>> Hi,
>>>>
>>>> Gilles Chanteperdrix wrote:
>>>>> Wolfgang Mauerer wrote:
>>>>>> So that means, in essence, that you would accept probabilistic
>>>>>> algorithms in realtime context?
>>>>> Ah, today's troll!
>>>> though it seems that I have to replace Jan this time ;-)
>>>>> As I think I explained, the use of a seqlock in real-time context
>>>>> when
>>>>> the seqlock writer only happens in linux context is not
>>>>> probabilistic.
>>>>> It will work every time the first pass.
>>>> I still don't see why it should succeed every time: What about
>>>> the case that the Linux kernel on CPU0 updates the data, while
>>>> Xenomai accesses them on another CPU? This can lead to
>>>> inconsistent data, and they must be reread on the Xenomai side.
>>> Yeah, right. I was not thinking about SMP. But admit that in this
>>> case,
>>> there will be only one retry, there is nothing pathological.
that's right. Which makes it bounded again, so it's maybe
the best way to go.
>>>
>>>> I'm asking because if this case can not happen, then there's
>>>> nothing left to to as I have the code already at hand.
>>> You have reworked the nucleus timers handling to adapt to this new
>>> real-time clock ?
>> Nope. Sorry, I was a bit unclear: I'm just referring to the gtod
>> syscall that does the timer handling, Not any other adaptions.
>
> Ok, but what good is the gtod syscall if you can not use it as a time
> reference for other timing related services?
it suffices for our project's current purposes ;-)
But it's certainly not the full solution. Before, we
should have a decision wrt. the design issues, but I
won't be able to continue working on this before
mid of next week to look at the changed required for timer
handling and come up with code.
Cheers, Wolfgang
next prev parent reply other threads:[~2009-12-03 20:31 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-02 12:55 [Xenomai-core] Realtime gettimeofday() Wolfgang Mauerer
2009-12-02 13:23 ` Gilles Chanteperdrix
2009-12-02 13:43 ` Jan Kiszka
2009-12-02 14:15 ` Gilles Chanteperdrix
2009-12-02 14:31 ` Jan Kiszka
2009-12-02 14:35 ` Gilles Chanteperdrix
2009-12-02 14:55 ` Jan Kiszka
2009-12-02 15:03 ` Gilles Chanteperdrix
2009-12-02 15:16 ` Jan Kiszka
2009-12-02 16:08 ` Gilles Chanteperdrix
2009-12-02 16:23 ` Jan Kiszka
2009-12-02 16:59 ` Gilles Chanteperdrix
2009-12-02 20:54 ` Gilles Chanteperdrix
2009-12-02 22:03 ` Wolfgang Mauerer
2009-12-02 22:20 ` Gilles Chanteperdrix
2009-12-02 22:33 ` Gilles Chanteperdrix
2009-12-03 9:36 ` Wolfgang Mauerer
2009-12-03 10:50 ` Gilles Chanteperdrix
2009-12-03 13:11 ` Wolfgang Mauerer
2009-12-03 13:14 ` Gilles Chanteperdrix
2009-12-03 13:32 ` Wolfgang Mauerer
2009-12-03 13:38 ` Gilles Chanteperdrix
2009-12-03 20:31 ` Wolfgang Mauerer [this message]
2009-12-03 21:42 ` Gilles Chanteperdrix
2009-12-05 16:11 ` Philippe Gerum
2009-12-07 9:14 ` Jan Kiszka
2009-12-07 13:43 ` Gilles Chanteperdrix
2009-12-07 13:50 ` Jan Kiszka
2009-12-07 14:07 ` Philippe Gerum
2009-12-07 14:21 ` Wolfgang Mauerer
2009-12-15 15:00 ` Richard Cochran
2009-12-15 15:07 ` Gilles Chanteperdrix
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=4B18201D.30003@domain.hid \
--to=wm@domain.hid \
--cc=gilles.chanteperdrix@xenomai.org \
--cc=jan.kiszka@domain.hid \
--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.