From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andy Lutomirski Subject: Re: [PATCH v4 1/5] nohz_full: add support for "cpu_isolated" mode Date: Mon, 13 Jul 2015 13:40:58 -0700 Message-ID: References: <1436817481-8732-1-git-send-email-cmetcalf@ezchip.com> <1436817481-8732-2-git-send-email-cmetcalf@ezchip.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Return-path: In-Reply-To: <1436817481-8732-2-git-send-email-cmetcalf@ezchip.com> Sender: linux-doc-owner@vger.kernel.org To: Chris Metcalf Cc: Gilad Ben Yossef , Steven Rostedt , Ingo Molnar , Peter Zijlstra , Andrew Morton , Rik van Riel , Tejun Heo , Frederic Weisbecker , Thomas Gleixner , "Paul E. McKenney" , Christoph Lameter , Viresh Kumar , "linux-doc@vger.kernel.org" , Linux API , "linux-kernel@vger.kernel.org" List-Id: linux-api@vger.kernel.org On Mon, Jul 13, 2015 at 12:57 PM, Chris Metcalf wrote: > The existing nohz_full mode makes tradeoffs to minimize userspace > interruptions while still attempting to avoid overheads in the > kernel entry/exit path, to provide 100% kernel semantics, etc. > > However, some applications require a stronger commitment from the > kernel to avoid interruptions, in particular userspace device > driver style applications, such as high-speed networking code. > > This change introduces a framework to allow applications to elect > to have the stronger semantics as needed, specifying > prctl(PR_SET_CPU_ISOLATED, PR_CPU_ISOLATED_ENABLE) to do so. > Subsequent commits will add additional flags and additional > semantics. I thought the general consensus was that this should be the default behavior and that any associated bugs should be fixed. --Andy