Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753225AbdHKPfW (ORCPT ); Fri, 11 Aug 2017 11:35:22 -0400 Received: from resqmta-ch2-07v.sys.comcast.net ([69.252.207.39]:50072 "EHLO resqmta-ch2-07v.sys.comcast.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752631AbdHKPfV (ORCPT ); Fri, 11 Aug 2017 11:35:21 -0400 Date: Fri, 11 Aug 2017 10:35:19 -0500 (CDT) From: Christopher Lameter X-X-Sender: cl@nuc-kabylake To: Chris Metcalf cc: Mike Galbraith , Frederic Weisbecker , LKML , Peter Zijlstra , Thomas Gleixner , Luiz Capitulino , "Paul E . McKenney" , Ingo Molnar , Rik van Riel , Wanpeng Li Subject: Re: [RFC PATCH 0/9] Introduce housekeeping subsystem In-Reply-To: <3ff0c384-dcd9-41e5-c7cc-43c856a4a51e@mellanox.com> Message-ID: References: <1500643290-25842-1-git-send-email-fweisbec@gmail.com> <20170810125437.GA8754@lerouge> <3398d7d6-74c2-4918-ae3d-aa5a2e3a12dd@mellanox.com> <1502433388.16425.9.camel@gmx.de> <3ff0c384-dcd9-41e5-c7cc-43c856a4a51e@mellanox.com> User-Agent: Alpine 2.20 (DEB 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-CMAE-Envelope: MS4wfP6iITpgnCk9E494KEaPfk/PozQPTqOcYo6pkqyOUgB3w+VWtFVliulW6C7KrI8HSoSkxHJhyNjAX5lPIl0a7kRiKSnWg+fB4GY1+rm7JvN618F2z0/j s82XK6BU9CvO5GPacEkZ0hY63d5GFpSlOaS9MFi32absFc2YOmTa+Ya6XfIyl5boCF5+X06E0bfoY44b+Vb108oRaQUjeIJ2CCjxLnxwyutL1IRWy/LPe5qV OgcbUb5qZztwNxwik25ldv3lq9S7ngmiU/MOVssM1v/xDQhjQz5QJaneSiuN9YxWckGSFqJttmOjs0y6yScvyuA+Pm23izFZs7mGI8ej6zrJdSUEmBT5dlnV vk99JbkiTd6PmXvJZYBwbuySevRrnJ4uMZ9hjxOmLGge8Z+DQHPvaUGXXzYWxKia7Jqdy1mb1xcAAeCItD8Qe+VQ/rEi0+pKE8YiLohFXZ+/u4IIOF3pUudV yNRvjxBNbc5dbxDC Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1062 Lines: 24 On Fri, 11 Aug 2017, Chris Metcalf wrote: > > > Maybe a CONFIG_HOUSEKEEPING_BOOT_ONLY as a way to restrict housekeeping > > > by default to just the boot cpu. In conjunction with NOHZ_FULL_ALL you > > > would > > > then get the expected semantics. > > A big box with only the boot cpu for housekeeping is likely screwed. > > Fair point - this kind of configuration would be primarily useful for > dedicated systems that were running a high-traffic-rate networking > application on many cores, for example. In this mode you don't end up > putting a lot of burden on the housekeeping core. In any case, > probably not worth adding an additional kernel config for. The standard server config at this point is a two NUMA node with lots of cores on each. For such a thing a single housekeeping cpu is usually sufficient. Having a rather large number of NUMA nodes is unusual. The question is also what is considered a "large" system at this point? Lots of cores? Lots of NUMA nodes? Ah, Chris since you are here: What is happening with the dataplane patches?