From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <kostja.osipov@gmail.com>
Received: from mail-lj1-f193.google.com (mail-lj1-f193.google.com
 [209.85.208.193])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (No client certificate requested)
 by dev.tarantool.org (Postfix) with ESMTPS id 8C1F846970E
 for <tarantool-patches@dev.tarantool.org>;
 Mon, 23 Dec 2019 15:55:22 +0300 (MSK)
Received: by mail-lj1-f193.google.com with SMTP id y6so9637034lji.0
 for <tarantool-patches@dev.tarantool.org>;
 Mon, 23 Dec 2019 04:55:22 -0800 (PST)
Date: Mon, 23 Dec 2019 15:55:19 +0300
From: Konstantin Osipov <kostja.osipov@gmail.com>
Message-ID: <20191223125519.GA25824@atlas>
References: <73ebdf94c8f03fca216de9141c6541870b1ed938.1575390549.git.lvasiliev@tarantool.org>
 <20191203180257.GA4364@atlas>
 <65b9d108-fe36-1c9b-82c0-60e98efce658@tarantool.org>
 <20191205072706.GA16690@atlas>
 <442799bc-16a2-d5db-dc8c-d4663adfbe81@tarantool.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <442799bc-16a2-d5db-dc8c-d4663adfbe81@tarantool.org>
Subject: Re: [Tarantool-patches] [PATCH] Add a cancellation guard to cpipe
 flush callback
List-Id: Tarantool development patches <tarantool-patches.dev.tarantool.org>
List-Unsubscribe: <https://lists.tarantool.org/mailman/options/tarantool-patches>, 
 <mailto:tarantool-patches-request@dev.tarantool.org?subject=unsubscribe>
List-Archive: <https://lists.tarantool.org/pipermail/tarantool-patches/>
List-Post: <mailto:tarantool-patches@dev.tarantool.org>
List-Help: <mailto:tarantool-patches-request@dev.tarantool.org?subject=help>
List-Subscribe: <https://lists.tarantool.org/mailman/listinfo/tarantool-patches>, 
 <mailto:tarantool-patches-request@dev.tarantool.org?subject=subscribe>
To: Leonid Vasiliev <lvasiliev@tarantool.org>
Cc: tarantool-patches@dev.tarantool.org

* Leonid Vasiliev <lvasiliev@tarantool.org> [19/12/23 15:48]:
> +	while(hang_endpoint.mutex.__data.__lock < 2) {
> +		usleep(100);
> +	}

How does this work? Is there a way to not look inside mutex?

-- 
Konstantin Osipov, Moscow, Russia