[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20170620.155526.1175661303325942822.davem@davemloft.net>
Date: Tue, 20 Jun 2017 15:55:26 -0400 (EDT)
From: David Miller <davem@...emloft.net>
To: tj@...nel.org
Cc: nborisov@...e.com, jbacik@...com, linux-kernel@...r.kernel.org,
mgorman@...hsingularity.net, clm@...com, dsterba@...e.com,
darrick.wong@...cle.com, jack@...e.com, axboe@...com,
linux-mm@...ck.org
Subject: Re: [PATCH] percpu_counter: Rename __percpu_counter_add to
percpu_counter_add_batch
From: Tejun Heo <tj@...nel.org>
Date: Tue, 20 Jun 2017 15:47:59 -0400
> From 104b4e5139fe384431ac11c3b8a6cf4a529edf4a Mon Sep 17 00:00:00 2001
> From: Nikolay Borisov <nborisov@...e.com>
> Date: Tue, 20 Jun 2017 21:01:20 +0300
>
> Currently, percpu_counter_add is a wrapper around __percpu_counter_add
> which is preempt safe due to explicit calls to preempt_disable. Given
> how __ prefix is used in percpu related interfaces, the naming
> unfortunately creates the false sense that __percpu_counter_add is
> less safe than percpu_counter_add. In terms of context-safety,
> they're equivalent. The only difference is that the __ version takes
> a batch parameter.
>
> Make this a bit more explicit by just renaming __percpu_counter_add to
> percpu_counter_add_batch.
>
> This patch doesn't cause any functional changes.
>
> tj: Minor updates to patch description for clarity. Cosmetic
> indentation updates.
>
> Signed-off-by: Nikolay Borisov <nborisov@...e.com>
> Signed-off-by: Tejun Heo <tj@...nel.org>
Acked-by: David S. Miller <davem@...emloft.net>
Powered by blists - more mailing lists