Hi Manfred,Good idea, I have updated the comments.
On Sat, May 10, 2014 at 12:03 PM, Manfred Spraul
<manfred@xxxxxxxxxxxxxxxx> wrote:
Hi all,Perhaps it's woth noting here that the man page is also pretty close
According to the man page of semop(), semzcnt or semncnt are increased
exactly for the operation that couldn't proceed.
to the POSIX text that describes semzcnt and semncnt. Form the SUSv4
<sys/sem.h> spec:
semncnt: number of processes waiting for semval to become
greater than current value.
semzcnt: Number of processes waiting for semval to become 0.
Unfortunately I have more or less given up writing specific tests, instead I use a generic "change" application that allows to create multi-semop operations.The Linux implementation always tried to be clever and to increase the countersAre any of those test cases in a form that could be used by other to
for all operations that might be the reason why a task sleeps.
The following patches fix that and make the code conform to the
documentation.
The series got fairly long, because I also noticed that semzcnt was calculated
incorrectly.
What do you think?
I ran a few test cases, and the semncnt and semzcnt counts now match
the expectation.
replicate your results? Also, are there any of those tests that could
go into the source tree?