On Sunday, July 07, 2013 6:22:18 pm Davide Italiano wrote:
> On Sun, Jul 7, 2013 at 2:34 PM, Konstantin Belousov
wrote:
> > On Sat, Jul 06, 2013 at 01:22:05AM +0200, Davide Italiano wrote:
> >> Hi,
> >> as a preliminary step in the implementation of adaptive spinning for
> >> umtx, I'm switching
On Sun, Jul 7, 2013 at 2:34 PM, Konstantin Belousov wrote:
> On Sat, Jul 06, 2013 at 01:22:05AM +0200, Davide Italiano wrote:
>> Hi,
>> as a preliminary step in the implementation of adaptive spinning for
>> umtx, I'm switching the pthread/umtx code so that a thread that
>> acquires a pthread_mute
On Sun, Jul 7, 2013 at 9:47 AM, Julian Elischer wrote:
> On 7/6/13 7:22 AM, Davide Italiano wrote:
>>
>> Hi,
>> as a preliminary step in the implementation of adaptive spinning for
>> umtx, I'm switching the pthread/umtx code so that a thread that
>> acquires a pthread_mutex writes the address of
On 7/6/13 7:22 AM, Davide Italiano wrote:
Hi,
as a preliminary step in the implementation of adaptive spinning for
umtx, I'm switching the pthread/umtx code so that a thread that
acquires a pthread_mutex writes the address of struct pthread in the
owner field of the lock instead of the thread id
On Sat, Jul 06, 2013 at 01:22:05AM +0200, Davide Italiano wrote:
> Hi,
> as a preliminary step in the implementation of adaptive spinning for
> umtx, I'm switching the pthread/umtx code so that a thread that
> acquires a pthread_mutex writes the address of struct pthread in the
> owner field of the
Hi,
as a preliminary step in the implementation of adaptive spinning for
umtx, I'm switching the pthread/umtx code so that a thread that
acquires a pthread_mutex writes the address of struct pthread in the
owner field of the lock instead of the thread id (tid). This is
because having struct pthread
