From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933935AbcA0RhA (ORCPT ); Wed, 27 Jan 2016 12:37:00 -0500 Received: from mail.efficios.com ([78.47.125.74]:45791 "EHLO mail.efficios.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933720AbcA0Rg6 (ORCPT ); Wed, 27 Jan 2016 12:36:58 -0500 Date: Wed, 27 Jan 2016 17:36:48 +0000 (UTC) From: Mathieu Desnoyers To: Thomas Gleixner Cc: Josh Triplett , Paul Turner , Andrew Hunter , Peter Zijlstra , linux-kernel@vger.kernel.org, linux-api , Andy Lutomirski , Andi Kleen , Dave Watson , Chris Lameter , Ingo Molnar , Ben Maurer , rostedt , "Paul E. McKenney" , Linus Torvalds , Andrew Morton , Russell King , Catalin Marinas , Will Deacon , Michael Kerrisk Message-ID: <2049061625.6140.1453916208296.JavaMail.zimbra@efficios.com> In-Reply-To: References: <1453913683-28915-1-git-send-email-mathieu.desnoyers@efficios.com> <1453913683-28915-2-git-send-email-mathieu.desnoyers@efficios.com> <20160127172044.GA7514@cloud> Subject: Re: [RFC PATCH v2 1/3] getcpu_cache system call: cache CPU number of running thread MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [78.47.125.74] X-Mailer: Zimbra 8.6.0_GA_1178 (ZimbraWebClient - FF43 (Linux)/8.6.0_GA_1178) Thread-Topic: getcpu_cache system call: cache CPU number of running thread Thread-Index: LKQhg6mJtd7mz9sE6l+d9Dnrew250w== Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org ----- On Jan 27, 2016, at 12:24 PM, Thomas Gleixner tglx@linutronix.de wrote: > On Wed, 27 Jan 2016, Josh Triplett wrote: >> With the dynamic allocation removed, this seems sensible to me. One >> minor nit: s/int32_t/uint32_t/g, since a location intended to hold a CPU >> number should never need to hold a negative number. > > You try to block the future of computing: https://lwn.net/Articles/638673/ Besides impossible architectures, there is actually a use-case for signedness here. It makes it possible to initialize the cpu number cache to a negative value, e.g. -1, in userspace. Then, a check for value < 0 can be used to figure out cases where the getcpu_cache system call is not implemented, and where a fallback (vdso or getcpu syscall) needs to be used. This is why I have chosen a signed type for the cpu cache so far. Thoughts ? Thanks, Mathieu -- Mathieu Desnoyers EfficiOS Inc. http://www.efficios.com