From: adriano <a.verardo@tecmav.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] a pair nec bugs
Date: Sat, 4 Jun 2011 20:12:34 +0200 [thread overview]
Message-ID: <4DEA7592.6030802@tecmav.com> (raw)
In-Reply-To: <f6bb6caf8b5d268f957a75db4b958a38@terzarima.net>
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
next prev parent reply other threads:[~2011-06-04 18:12 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-20 1:30 erik quanstrom
2011-05-20 5:05 ` [9fans] a pair nsec bugs erik quanstrom
2011-05-20 10:43 ` [9fans] a pair nec bugs ron minnich
2011-05-20 10:52 ` roger peppe
2011-05-20 10:57 ` ron minnich
2011-05-20 12:47 ` erik quanstrom
2011-05-20 19:03 ` ron minnich
2011-05-20 19:16 ` erik quanstrom
2011-05-21 3:27 ` erik quanstrom
2011-05-21 9:59 ` Charles Forsyth
2011-05-21 12:16 ` erik quanstrom
2011-05-21 21:50 ` erik quanstrom
2011-05-21 22:14 ` Charles Forsyth
2011-05-22 3:06 ` erik quanstrom
2011-05-22 13:30 ` Charles Forsyth
2011-06-02 19:16 ` erik quanstrom
2011-06-03 9:52 ` Charles Forsyth
2011-06-04 18:12 ` adriano [this message]
2011-06-03 13:13 erik quanstrom
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=4DEA7592.6030802@tecmav.com \
--to=a.verardo@tecmav.com \
--cc=9fans@9fans.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).