From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S934284AbcA0SEH (ORCPT ); Wed, 27 Jan 2016 13:04:07 -0500 Received: from relay4-d.mail.gandi.net ([217.70.183.196]:46463 "EHLO relay4-d.mail.gandi.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S934012AbcA0SED (ORCPT ); Wed, 27 Jan 2016 13:04:03 -0500 Date: Wed, 27 Jan 2016 10:03:53 -0800 From: Josh Triplett To: Mathieu Desnoyers Cc: Thomas Gleixner , 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 Subject: Re: [RFC PATCH v2 1/3] getcpu_cache system call: cache CPU number of running thread Message-ID: <20160127180353.GB7514@cloud> References: <1453913683-28915-1-git-send-email-mathieu.desnoyers@efficios.com> <1453913683-28915-2-git-send-email-mathieu.desnoyers@efficios.com> <20160127172044.GA7514@cloud> <2049061625.6140.1453916208296.JavaMail.zimbra@efficios.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2049061625.6140.1453916208296.JavaMail.zimbra@efficios.com> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Jan 27, 2016 at 05:36:48PM +0000, Mathieu Desnoyers wrote: > ----- 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. If getcpu_cache doesn't exist, you'll get ENOSYS. If getcpu_cache returns 0, then you can assume the kernel will give you a valid CPU number. - Josh Triplett