From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752758AbcKRKsB (ORCPT ); Fri, 18 Nov 2016 05:48:01 -0500 Received: from mga03.intel.com ([134.134.136.65]:28342 "EHLO mga03.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752553AbcKRKr6 (ORCPT ); Fri, 18 Nov 2016 05:47:58 -0500 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.31,509,1473145200"; d="scan'208";a="1087034157" From: "Reshetova, Elena" To: Peter Zijlstra , "gregkh@linuxfoundation.org" , "keescook@chromium.org" , "will.deacon@arm.com" , "arnd@arndb.de" , "tglx@linutronix.de" , "mingo@kernel.org" , "hpa@zytor.com" , "dave@progbits.org" CC: "linux-kernel@vger.kernel.org" Subject: RE: [RFC][PATCH 7/7] kref: Implement using refcount_t Thread-Topic: [RFC][PATCH 7/7] kref: Implement using refcount_t Thread-Index: AQHSPp8nZI2aGULSnkSyKlUn6xiKNqDeiSUQgAALYCA= Date: Fri, 18 Nov 2016 10:47:40 +0000 Message-ID: <2236FBA76BA1254E88B949DDB74E612B41C14924@IRSMSX102.ger.corp.intel.com> References: <20161114173946.501528675@infradead.org> <20161114174446.832175072@infradead.org> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [163.33.239.182] Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by mail.home.local id uAIAmBvX017514 >Provide refcount_t, an atomic_t like primitive built just for refcounting. >It provides overflow and underflow checks as well as saturation semantics such that when it overflows, we'll never attempt to free it again, ever. >Peter do you have the changes to the refcount_t interface compare to the version in this patch? >We are now starting working on atomic_t --> refcount_t conversions and it would save a bit of work to have latest version from you that we can be based upon. Oh, and if we define refcount_t to be just atomic_t underneath, what about the other atomic_long_t, local_t and atomic64_t cases when it is used for recounting? I don't feel good just simply changing them to become atomic_t under refcount_t wrapper.....