Received: by 2002:a25:d7c1:0:0:0:0:0 with SMTP id o184csp3517673ybg; Mon, 28 Oct 2019 14:12:46 -0700 (PDT) X-Google-Smtp-Source: APXvYqw+Gtpjm24OiGMxF/egYMYuOqPaLJ39KzZ9hF2AvWMyQc6Vl7ZSHdjEh87sJ0EYBtheBslN X-Received: by 2002:a05:6402:696:: with SMTP id f22mr10542573edy.104.1572297166218; Mon, 28 Oct 2019 14:12:46 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1572297166; cv=none; d=google.com; s=arc-20160816; b=TlWk2H5rTui1WvQtTwW4nBQbvdolX+9Z3VABbKc2iDirQf/tcLm2EIQGAxJQ4Ng9D9 gskTKUGRleh8r+j0gUmWuIn8Xfmq4ySHbaIvQ8BIFc2O3RkKWvv+3zBX83lYFQPxGQD3 zKor4SPKezgmlXNvE57wJvgpbANAWKBRM1ssfWxbVT7ZkbQkNL3Fw7AgqvVD1OiPgvgX DVCcC/rynzdRJrA4hgVYYbZyOpIICxJ72wR1q+equRlgGF+BODwW5qv3W7DV4nmUaPQY h2OV/VYL0XqTkB4ysHfU36uOh8Q5DNDogsl6D/wG9WnjhRYRLQjaso2nXK42Yb9UKiT3 WVwQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature; bh=+zzbwsC3kl/aTMGuhmhBSPoELXj9zKaAruwXWjNUJLA=; b=a6TSUSYHYRBckmJipc6oKdoi7E2d8CN2HKAbvUrj2CDdlnQoysKS7YJv6/BcBIiZ8C MM78RDXmKDAeJ/v6BMgcgaDfSZA9w37rCQi1ucoKp10+0nzM9YJEplMqqumWfo8Lpib5 2amTcaxpVj1zHaOAk9mCfPMLrmuaunHINTV9TtXXNKbcn5qgGMSNETSfXdcIWB+8mz42 E+GHmjc6FGMNwibE5L+742ibSGIRphCFad3fpHC7lpp3DpuwXYSiyX47cc+GMts5JoLE 1GjBFFWuA8MsO5R60SL9Myreix5kZDxV/Qchmn5lzn+cjj4HmKn8JCobt8oKDC6oIS0j vImg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=t5r3BrfQ; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id c17si8351607edc.384.2019.10.28.14.12.22; Mon, 28 Oct 2019 14:12:46 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=t5r3BrfQ; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1732272AbfJ1PhH (ORCPT + 99 others); Mon, 28 Oct 2019 11:37:07 -0400 Received: from mail.kernel.org ([198.145.29.99]:55540 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726025AbfJ1PhG (ORCPT ); Mon, 28 Oct 2019 11:37:06 -0400 Received: from localhost (unknown [91.217.168.176]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id C1B3520578; Mon, 28 Oct 2019 15:37:05 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1572277026; bh=g38VoI5LJrASchwjNi5RYmGYL3WYNwPkOBYh7bPUb0k=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=t5r3BrfQocbPBwDmaCn9MKFT3W2EIB4MOStdx0SbBZnhjQxU2GHUBKULWWAFmWjsh NsF0fy2NObcHK1HCgor/E5h9mWr0eI4WSNx9MgbyTbULxXNR1uC6AWntxV4/xcPwpE GeK6HaAVVJyabCZHsCWszG3TW3RY04zrY8bpkhJQ= Date: Mon, 28 Oct 2019 16:37:04 +0100 From: Greg KH To: Davidlohr Bueso Cc: Stefan Wahren , eric@anholt.net, linux-kernel@vger.kernel.org, devel@driverdev.osuosl.org Subject: Re: [PATCH] staging: vc04_services: replace g_free_fragments_mutex with spinlock Message-ID: <20191028153704.GA134005@kroah.com> References: <20191027221530.12080-1-dave@stgolabs.net> <576df522-f012-9dd1-9dcc-b7e444e82ac6@gmx.net> <20191028152108.bjliafudxn3llysv@linux-p48b> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20191028152108.bjliafudxn3llysv@linux-p48b> User-Agent: Mutt/1.12.2 (2019-09-21) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Oct 28, 2019 at 08:21:08AM -0700, Davidlohr Bueso wrote: > On Mon, 28 Oct 2019, Stefan Wahren wrote: > > > Hi Davidlohr, > > > > Am 27.10.19 um 23:15 schrieb Davidlohr Bueso: > > > There seems no need to be using a semaphore, or a sleeping lock > > > in the first place: critical region is extremely short, does not > > > call into any blocking calls and furthermore lock and unlocking > > > operations occur in the same context. > > > > > > Get rid of another semaphore user by replacing it with a spinlock. > > > > > > Signed-off-by: Davidlohr Bueso > > > --- > > > This is in an effort to further reduce semaphore users in the kernel. > > > > > thanks for this. Could please also send this to devel@driverdev.osuosl.org? > > Ccing. I don't see a patch here :(