From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751551AbbD2W0c (ORCPT ); Wed, 29 Apr 2015 18:26:32 -0400 Received: from mail.linuxfoundation.org ([140.211.169.12]:59251 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751023AbbD2W0a (ORCPT ); Wed, 29 Apr 2015 18:26:30 -0400 Date: Wed, 29 Apr 2015 15:26:29 -0700 From: Andrew Morton To: Chris Metcalf Cc: Frederic Weisbecker , Don Zickus , Ingo Molnar , Andrew Jones , chai wen , Ulrich Obergfell , Fabian Frederick , Aaron Tomlin , Ben Zhang , "Christoph Lameter" , Gilad Ben-Yossef , "Steven Rostedt" , , "Jonathan Corbet" , , Thomas Gleixner , Peter Zijlstra Subject: Re: [PATCH v9 2/3] watchdog: add watchdog_cpumask sysctl to assist nohz Message-Id: <20150429152629.74212a1808833d979c7b797d@linux-foundation.org> In-Reply-To: <1429295838-6328-2-git-send-email-cmetcalf@ezchip.com> References: <20150416152808.GA16270@lerouge> <1429295838-6328-1-git-send-email-cmetcalf@ezchip.com> <1429295838-6328-2-git-send-email-cmetcalf@ezchip.com> X-Mailer: Sylpheed 3.4.1 (GTK+ 2.24.23; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 17 Apr 2015 14:37:17 -0400 Chris Metcalf wrote: > Change the default behavior of watchdog so it only runs on the > housekeeping cores when nohz_full is enabled at build and boot time. > Allow modifying the set of cores the watchdog is currently running > on with a new kernel.watchdog_cpumask sysctl. > > If we allowed the watchdog to run on nohz_full cores, the timer > interrupts and scheduler work would prevent the desired tickless > operation on those cores. But if we disable the watchdog globally, > then the housekeeping cores can't benefit from the watchdog > functionality. So we allow disabling it only on some cores. > See Documentation/lockup-watchdogs.txt for more information. Could you please expand on the patch motivation? "would prevent the desired tickless operation on those cores" is quite vague. Exactly what userspace-visible problem is the current implementation causing and how does the patchset improve things? If any of this is quantifiable (wakeups/sec, joules/hour etc) then some attempt to perform those measurements would also be useful.