From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pg0-f69.google.com (mail-pg0-f69.google.com [74.125.83.69]) by kanga.kvack.org (Postfix) with ESMTP id 82D7F6B0033 for ; Sun, 22 Jan 2017 19:47:04 -0500 (EST) Received: by mail-pg0-f69.google.com with SMTP id f5so180652426pgi.1 for ; Sun, 22 Jan 2017 16:47:04 -0800 (PST) Received: from mx0a-001b2d01.pphosted.com (mx0a-001b2d01.pphosted.com. [148.163.156.1]) by mx.google.com with ESMTPS id a33si13935861pld.29.2017.01.22.16.47.03 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 22 Jan 2017 16:47:03 -0800 (PST) Received: from pps.filterd (m0098409.ppops.net [127.0.0.1]) by mx0a-001b2d01.pphosted.com (8.16.0.20/8.16.0.20) with SMTP id v0N0hXud092813 for ; Sun, 22 Jan 2017 19:47:03 -0500 Received: from e38.co.us.ibm.com (e38.co.us.ibm.com [32.97.110.159]) by mx0a-001b2d01.pphosted.com with ESMTP id 2843tyrhc4-1 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=NOT) for ; Sun, 22 Jan 2017 19:47:02 -0500 Received: from localhost by e38.co.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Sun, 22 Jan 2017 17:47:02 -0700 Date: Sun, 22 Jan 2017 16:46:57 -0800 From: "Paul E. McKenney" Subject: Re: [PATCH RFC] mm: Rename SLAB_DESTROY_BY_RCU to SLAB_TYPESAFE_BY_RCU Reply-To: paulmck@linux.vnet.ibm.com References: <20170118110731.GA15949@linux.vnet.ibm.com> <20170118111201.GB29472@bombadil.infradead.org> <20170118221737.GP5238@linux.vnet.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Message-Id: <20170123004657.GT5238@linux.vnet.ibm.com> Sender: owner-linux-mm@kvack.org List-ID: To: Christoph Lameter Cc: willy@infradead.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org, penberg@kernel.org, rientjes@google.com, iamjoonsoo.kim@lge.com, akpm@linux-foundation.org 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 Thanx, Paul -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750808AbdAWArE (ORCPT ); Sun, 22 Jan 2017 19:47:04 -0500 Received: from mx0a-001b2d01.pphosted.com ([148.163.156.1]:54382 "EHLO mx0a-001b2d01.pphosted.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750704AbdAWArD (ORCPT ); Sun, 22 Jan 2017 19:47:03 -0500 Date: Sun, 22 Jan 2017 16:46:57 -0800 From: "Paul E. McKenney" To: Christoph Lameter Cc: willy@infradead.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org, penberg@kernel.org, rientjes@google.com, iamjoonsoo.kim@lge.com, akpm@linux-foundation.org Subject: Re: [PATCH RFC] mm: Rename SLAB_DESTROY_BY_RCU to SLAB_TYPESAFE_BY_RCU Reply-To: paulmck@linux.vnet.ibm.com References: <20170118110731.GA15949@linux.vnet.ibm.com> <20170118111201.GB29472@bombadil.infradead.org> <20170118221737.GP5238@linux.vnet.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-TM-AS-GCONF: 00 X-Content-Scanned: Fidelis XPS MAILER x-cbid: 17012300-0028-0000-0000-000006D83095 X-IBM-SpamModules-Scores: X-IBM-SpamModules-Versions: BY=3.00006480; HX=3.00000240; KW=3.00000007; PH=3.00000004; SC=3.00000200; SDB=6.00811282; UDB=6.00395523; IPR=6.00588698; BA=6.00005082; NDR=6.00000001; ZLA=6.00000005; ZF=6.00000009; ZB=6.00000000; ZP=6.00000000; ZH=6.00000000; ZU=6.00000002; MB=3.00014007; XFM=3.00000011; UTC=2017-01-23 00:47:00 X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused x-cbparentid: 17012300-0029-0000-0000-000032EDF81C Message-Id: <20170123004657.GT5238@linux.vnet.ibm.com> X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2017-01-22_16:,, signatures=0 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 spamscore=0 suspectscore=0 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1612050000 definitions=main-1701230010 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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 Thanx, Paul