From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751037AbdCAGs1 (ORCPT ); Wed, 1 Mar 2017 01:48:27 -0500 Received: from LGEAMRELO13.lge.com ([156.147.23.53]:48525 "EHLO lgeamrelo13.lge.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750703AbdCAGsY (ORCPT ); Wed, 1 Mar 2017 01:48:24 -0500 X-Original-SENDERIP: 156.147.1.121 X-Original-MAILFROM: byungchul.park@lge.com X-Original-SENDERIP: 165.244.249.25 X-Original-MAILFROM: byungchul.park@lge.com X-Original-SENDERIP: 10.177.222.33 X-Original-MAILFROM: byungchul.park@lge.com Date: Wed, 1 Mar 2017 15:18:04 +0900 From: Byungchul Park To: Peter Zijlstra CC: , , , , , , , , , , Subject: Re: [PATCH v5 06/13] lockdep: Implement crossrelease feature Message-ID: <20170301061804.GF11663@X58A-UD3R> References: <1484745459-2055-1-git-send-email-byungchul.park@lge.com> <1484745459-2055-7-git-send-email-byungchul.park@lge.com> <20170228154900.GL5680@worktop> <20170301051706.GD11663@X58A-UD3R> MIME-Version: 1.0 In-Reply-To: <20170301051706.GD11663@X58A-UD3R> User-Agent: Mutt/1.5.21 (2010-09-15) X-MIMETrack: Itemize by SMTP Server on LGEKRMHUB04/LGE/LG Group(Release 8.5.3FP6|November 21, 2013) at 2017/03/01 15:18:19, Serialize by Router on LGEKRMHUB04/LGE/LG Group(Release 8.5.3FP6|November 21, 2013) at 2017/03/01 15:18:19, Serialize complete at 2017/03/01 15:18:19 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Mar 01, 2017 at 02:17:07PM +0900, Byungchul Park wrote: > On Tue, Feb 28, 2017 at 04:49:00PM +0100, Peter Zijlstra wrote: > > On Wed, Jan 18, 2017 at 10:17:32PM +0900, Byungchul Park wrote: > > > > > +struct cross_lock { > > > + /* > > > + * When more than one acquisition of crosslocks are overlapped, > > > + * we do actual commit only when ref == 0. > > > + */ > > > + atomic_t ref; > > > > That comment doesn't seem right, should that be: ref != 0 ? > > Also; would it not be much clearer to call this: nr_blocked, or waiters > > or something along those lines, because that is what it appears to be. Honestly, I forgot why I introduced the ref.. I will remove the ref next spin, and handle waiters in another way. Thank you, Byungchul