Re: high frequency time stamping (Was: Simple Components 4.12 with MQTT implementation released)

[Georg Bauhaus <bauhaus@futureapps.invalid>]

On 19.04.16 15:35, Dmitry A. Kazakov wrote:
> On 19/04/2016 14:59, G.B. wrote:
>> On 19.04.16 14:43, Dmitry A. Kazakov wrote:
>>> It is a value and a time stamp, because data are oversampled. There is
>>> no way a conventional OS could respond to each change at this rate.
>>
>> Is it possible to have a volatile variable T representing
>> some point in time and a CAS discipline so that
>>
>> 1. there is one task that updates T at regular intervals and
>>
>> 2. another task that reads T for stamping items more frequently
>>     than the first would write updates?
>
> It is an interesting question. Do you mean CAS = content-addressable storage?

Coincidence! While I'd expect the time storing variable to be located
in some kind of privileged location, I had meant CAS to refer to some
thread-safe update mechanism. I now notice that maybe mutex via volatile
storage might already be in place.
  All of this would be based on the assumption that reading the time via
system is much more costly than just reading a volatile variable,
while perhaps adding a sequence number for ordering the stamped items
within one time frame. Also separates problems and solutions, as you
indicated. Nothing new, I guess.
  (For a case at hand, the measuring devices will be collecting only
about 10-200 signals/second, yet mustn't have their batteries emptied.)