From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-yb1-f196.google.com ([209.85.219.196]:35572 "EHLO mail-yb1-f196.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726828AbeIRSWv (ORCPT ); Tue, 18 Sep 2018 14:22:51 -0400 Date: Tue, 18 Sep 2018 05:50:21 -0700 From: Tejun Heo To: Ming Lei Cc: linux-kernel@vger.kernel.org, Jianchao Wang , Kent Overstreet , linux-block@vger.kernel.org Subject: Re: [PATCH 2/4] lib/percpu-refcount: introduce percpu_ref_resurge() Message-ID: <20180918125021.GB902964@devbig004.ftw2.facebook.com> References: <20180918101946.13329-1-ming.lei@redhat.com> <20180918101946.13329-3-ming.lei@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <20180918101946.13329-3-ming.lei@redhat.com> Sender: linux-block-owner@vger.kernel.org List-Id: linux-block@vger.kernel.org On Tue, Sep 18, 2018 at 06:19:44PM +0800, Ming Lei wrote: > Now percpu_ref_reinit() can only be done on one percpu refcounter when it > drops zero. And the limit shouldn't be so strict, and it is quite > straightforward that we can do it when the refcount doesn't drop zero > because it is at atomic mode. > > This patch introduces percpu_ref_resurge() in which the above limit is > relaxed, so we may avoid extra change[1] for NVMe timeout's requirement. For now, Nacked-by: Tejun Heo Please see the original discussion thread. Thanks. -- tejun