[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1485363887.5145.27.camel@edumazet-glaptop3.roam.corp.google.com>
Date: Wed, 25 Jan 2017 09:04:47 -0800
From: Eric Dumazet <eric.dumazet@...il.com>
To: Christoph Lameter <cl@...ux.com>
Cc: "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
willy@...radead.org, linux-kernel@...r.kernel.org,
linux-mm@...ck.org, penberg@...nel.org, rientjes@...gle.com,
iamjoonsoo.kim@....com, akpm@...ux-foundation.org
Subject: Re: [PATCH RFC] mm: Rename SLAB_DESTROY_BY_RCU to
SLAB_TYPESAFE_BY_RCU
On Wed, 2017-01-25 at 10:45 -0600, Christoph Lameter wrote:
> On Sun, 22 Jan 2017, Paul E. McKenney wrote:
>
> > On Wed, Jan 18, 2017 at 06:00:24PM -0600, Christoph Lameter wrote:
> > > On Wed, 18 Jan 2017, Paul E. McKenney wrote:
> > >
> > > > Actually, slab is using RCU to provide type safety to those slab users
> > > > who request it.
> > >
> > > Typesafety is a side effect. The main idea here is that the object can
> > > still be accessed in RCU sections after another processor frees the
> > > object. We guarantee that the object is not freed but it may be reused
> > > for another object within the RCU period.
> > >
> > > Can we have a name that expresses all of that properly?
> >
> > But of course!!! "Type safety". http://wiki.c2.com/?TypeSafe
>
> Well that does not convey the idea that RCU is involved here.
>
> SLAB_DESTROY_RCU_TYPESAFE
Not clear why we need to change this very fine name ?
SLAB_DESTROY_BY_RCU was only used by few of us, we know damn well what
it means.
Consider we wont be able to change it in various web pages / archives /
changelogs.
Powered by blists - more mailing lists