From mboxrd@z Thu Jan 1 00:00:00 1970 From: Josh Triplett Subject: Re: [RFC PATCH v8 1/9] Restartable sequences system call Date: Fri, 19 Aug 2016 14:24:23 -0700 Message-ID: <20160819212423.623v5leqknfrxhpd@x> References: <1471637274-13583-1-git-send-email-mathieu.desnoyers@efficios.com> <1471637274-13583-2-git-send-email-mathieu.desnoyers@efficios.com> <20160819205611.GF5871@two.firstfloor.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <20160819205611.GF5871@two.firstfloor.org> Sender: linux-kernel-owner@vger.kernel.org To: Andi Kleen Cc: Linus Torvalds , Mathieu Desnoyers , Peter Zijlstra , "Paul E. McKenney" , Boqun Feng , Andy Lutomirski , Dave Watson , Linux Kernel Mailing List , Linux API , Paul Turner , Andrew Morton , Russell King , Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , Andrew Hunter , Chris Lameter , Ben Maurer , Steven Rostedt , Catalin Marinas List-Id: linux-api@vger.kernel.org On Fri, Aug 19, 2016 at 01:56:11PM -0700, Andi Kleen wrote: > > Nobody gets a cpu number just to get a cpu number - it's not a useful > > thing to benchmark. What does getcpu() so much that we care? > > malloc is the primary target I believe. Saves lots of memory to keep > caches per CPU rather than per thread. Also improves locality; that does seem like a good idea. Has anyone written and tested the corresponding changes to a malloc implementation? - Josh Triplett