Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756756AbdLOPFT (ORCPT ); Fri, 15 Dec 2017 10:05:19 -0500 Received: from resqmta-ch2-06v.sys.comcast.net ([69.252.207.38]:50658 "EHLO resqmta-ch2-06v.sys.comcast.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756747AbdLOPFM (ORCPT ); Fri, 15 Dec 2017 10:05:12 -0500 Date: Fri, 15 Dec 2017 09:05:09 -0600 (CST) From: Christopher Lameter X-X-Sender: cl@nuc-kabylake To: Peter Zijlstra cc: Mathieu Desnoyers , "Paul E. McKenney" , Boqun Feng , Andy Lutomirski , Dave Watson , linux-kernel , linux-api , Paul Turner , Andrew Morton , Russell King , Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , Andrew Hunter , Andi Kleen , Ben Maurer , rostedt , Josh Triplett , Linus Torvalds , Catalin Marinas , Will Deacon , Michael Kerrisk , Alexander Viro Subject: Re: [RFC PATCH for 4.16 02/21] rseq: Introduce restartable sequences system call (v12) In-Reply-To: <20171214212023.GJ3326@worktop> Message-ID: References: <20171214161403.30643-1-mathieu.desnoyers@efficios.com> <20171214161403.30643-3-mathieu.desnoyers@efficios.com> <12046460.34426.1513275177081.JavaMail.zimbra@efficios.com> <1537392285.34532.1513279478488.JavaMail.zimbra@efficios.com> <20171214212023.GJ3326@worktop> User-Agent: Alpine 2.20 (DEB 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-CMAE-Envelope: MS4wfAVljSyZuHubGp/DMpf2Yd4+2b8SB30bIp3FHB/LIqp5R0BlPqpyPjqYDwg4Oj8eZZit1t1AiF9uFDRUCF8gsGPBXlkuLqBF7UnBXLsdaYKaZrBqHrSU W+ciQ3obnGTYnQQzoZpa7rKUB0tM9RlETAbkfdp4Lp7TjreD9Qnk2W6SPRfOJs8roH7LjcRhqdKlueP9irPZReUtu08a5yp3FVAjJ0jaGa1lIePNu18a8f2B xpVXV+pnNox677emUuJLZ+HsjtFLuwb20Wc/9HWT1fNXyxE/36tGEoAZ+QjinmU5PSzTnga73dHTSdNOXpxKIzaP7zXkQXJ1LMD6iwwZa5lgNFV6wnzPhdru PWd2zd9R7CJYuXTA4WpkOstONkL56BpbHDpIyjtw90cPSP+Mv9+6FDYo1qFpIpa4UJwTUthtcTI/ctmmOU0WMwC2DzUJMVOYZ1RQxK3cZqweA6159k+3xIN2 QTzaMwkRQI2w1CCa8LTxS4hBEaTIgC6dCz5F5RuG2son+FxIwqDaQJ3HTxGcz+DguKGayqRBanMs6O56OiZlAX6wKRdQUFHJRBLHOFMicbCsa6Ld3KIpiK9a cJouQ8CkfKEQ46uQcPDo4mO9oLLrt5E0F/jCrYZ1yNfRTeUKVD8u2165rpuX9gdtnENk4g2nUIrXLRi19mGP4IUdb+/oZUl4XB4YIFTRvnesfq7U1Rt1Mrrh tV5bsuiU1j5XfQECtixRx+XBiy2f2zLbl+qX87EQgZIplBLrbYvYRIu+KUa+T8hFGwH1ExvNdsdIB10+jkSLD96v1ytE7EwXWxMz8omXADSL9kKlEh9kJGfR rvBDB4Ikak+uCZeTrY0afAR8HBRpILRw6Kj6weDmOx6OOjfEwgCmFwQizuk2Hzrlzlf2dHWWeVjtCf5LUeU= Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 518 Lines: 12 On Thu, 14 Dec 2017, Peter Zijlstra wrote: > > But my company has extensive user space code that maintains a lot of > > counters and does other tricks to get full performance out of the > > hardware. Such a mechanism would also be good from user space. Why keep > > the good stuff only inside the kernel? > > Mathieu's proposal is for userspace, _only_ userspace. But what we were talking about are instructions that work effectively in kernel space whose efficiency restartable sequences could bring to user space.