Charles Forsyth wrote:
what about applications that need to get the nsec frequently?
*in those applications*, i write
Hi, all
Last month I had problems in a appl made up by 12 threads using a shared
file table.
Six of them continuosly get the time every 20..100 ms.
The last version of the appl worked perfectly since 2009, until I
changed a few details.
From that point on I frequently had a messy file table and sometimes a
crash,
with a overall behaviour depending on the hw, on the presence of debug
print(), on
the network load etc etc ...
With /dev/bintime unexpectedly closed and viewing the nsec() code, I
thought to a critical race too.
Two weeks ago I've slightly modified the application, to have separate
(RFFDG) fd tables per thread.
This way, in my specific appl, the problem seems to be avoided. All the
(15) machines work ok now.
adriano
