Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 17 Jul 2008 10:05:52 -0400
From:      John Baldwin <jhb@freebsd.org>
To:        freebsd-hackers@freebsd.org
Cc:        Michael B Allen <ioplex@gmail.com>
Subject:   Re: Pls sanity check my semtimedop(2) implementation
Message-ID:  <200807171005.53148.jhb@freebsd.org>
In-Reply-To: <78c6bd860807121611w4f6ab44brbebfffea9929682a@mail.gmail.com>
References:  <78c6bd860807121611w4f6ab44brbebfffea9929682a@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Saturday 12 July 2008 07:11:26 pm Michael B Allen wrote:
> Hi,
> 
> Below is a semtimedop(2) implementation that I'm using for FreeBSD. I
> was hoping someone could look it over and tell me if they think the
> implementation is sound.
> 
> The code seems to work ok but when stressing the FreeBSD build of my app
> I have managed to provoke errors related to concurrency (usually when a
> SIGALRM goes off). The Linux build works flawlessesly so I'm wondering
> about this one critical function that is different.
> 
> Do you think it would make any difference if I used
> ITIMER_VIRTUAL / SIGVTALRM instead of ITIMER_REAL / SIGALRM?
> 
> Or perhaps I should be using a different implementation entirely?

What specific races are you seeing?  The timer is firing too early, too late?

-- 
John Baldwin



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200807171005.53148.jhb>