From mboxrd@z Thu Jan 1 00:00:00 1970 From: Linus Torvalds Subject: Re: [RFC PATCH v8 1/9] Restartable sequences system call Date: Fri, 19 Aug 2016 14:32:13 -0700 Message-ID: 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> <20160819211946.GJ3482@linux.vnet.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Return-path: In-Reply-To: <20160819211946.GJ3482-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org> Sender: linux-api-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Paul McKenney Cc: Andi Kleen , Mathieu Desnoyers , Peter Zijlstra , 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 , Josh Triplett , Catalin Marinas List-Id: linux-api@vger.kernel.org On Fri, Aug 19, 2016 at 2:19 PM, Paul E. McKenney wrote: > On Fri, Aug 19, 2016 at 01:56:11PM -0700, Andi Kleen wrote: >> >> malloc is the primary target I believe. Saves lots of memory to keep >> caches per CPU rather than per thread. > > Agreed, a competent default malloc() in glibc would be a very nice change > from the current state. I agree that malloc can be a very good target for something like this, but it is also something that is quite complicated. A general-purpose allocator that could be used by glibc and has not just the performance but the debug stuff etc that people inevitably want is a big project. And then the people who have special needs end up writing their own allocators anyway, just because they care about certain layout and access patterns... Put another way: I'd really like to see some real numbers and use, rather than "this can be used for.." Linus