pcp
[Top] [All Lists]

Re: [pcp] libpcp multithreading - next steps

To: pcp@xxxxxxxxxxx
Subject: Re: [pcp] libpcp multithreading - next steps
From: Ken McDonell <kenj@xxxxxxxxxxxxxxxx>
Date: Wed, 27 Jul 2016 06:49:45 +1000
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <5797B9F7.2020701@xxxxxxxxxx>
References: <20160603155039.GB26460@xxxxxxxxxx> <578D1AE1.6060307@xxxxxxxxxx> <y0my44xksjb.fsf@xxxxxxxx> <57965C89.40401@xxxxxxxxxx> <20160725203257.GG5274@xxxxxxxxxx> <5797B9F7.2020701@xxxxxxxxxx>
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
On 27/07/16 05:28, Dave Brolley wrote:
On 07/25/2016 04:32 PM, Frank Ch. Eigler wrote:
Take for example, as reported back three months ago at [1]: the 4751
test case, as committed, was failing in that the last run timed out
and failed to produce output.

[1]  http://oss.sgi.com/archives/pcp/2016-04/msg00202.html
...
So let's start with the change referenced by [1] above. I'll have a look
at it.
...

This commit contains the contentious (in my mind) __pmHandleToPtr_unlocked() change ... reviewing this pre-empts the discussion about how to fix the context create/destroy race that I wanted us to resolve as a first step of restating this effort.

I also am unconvinced that any lock inversion existed in the original design and implementation and would like to understand that (if it exists) before we embark on a development path that relies on helgrind to find lock inversions rather than design to avoid lock inversions.

<Prev in Thread] Current Thread [Next in Thread>