From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932840Ab2GESgm (ORCPT ); Thu, 5 Jul 2012 14:36:42 -0400 Received: from mx2.parallels.com ([64.131.90.16]:49004 "EHLO mx2.parallels.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932104Ab2GESgk (ORCPT ); Thu, 5 Jul 2012 14:36:40 -0400 Message-ID: <4FF5DDFF.70900@parallels.com> Date: Thu, 5 Jul 2012 22:33:35 +0400 From: Glauber Costa User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:13.0) Gecko/20120615 Thunderbird/13.0.1 MIME-Version: 1.0 To: Johannes Weiner CC: Rik van Riel , Andrea Arcangeli , , , Hillf Danton , Dan Smith , Linus Torvalds , Andrew Morton , Thomas Gleixner , Ingo Molnar , Paul Turner , Suresh Siddha , Mike Galbraith , "Paul E. McKenney" , Lai Jiangshan , Bharata B Rao , Lee Schermerhorn , Srivatsa Vaddagiri , Christoph Lameter , Alex Shi , Mauricio Faria de Oliveira , Konrad Rzeszutek Wilk , Don Morris , Benjamin Herrenschmidt Subject: Re: [PATCH 09/40] autonuma: introduce kthread_bind_node() References: <1340888180-15355-1-git-send-email-aarcange@redhat.com> <1340888180-15355-10-git-send-email-aarcange@redhat.com> <4FEDCB7A.1060007@redhat.com> <20120629163820.GQ6676@redhat.com> <4FEDDE99.2090105@redhat.com> <20120705130902.GF7881@cmpxchg.org> In-Reply-To: <20120705130902.GF7881@cmpxchg.org> Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit X-Originating-IP: [109.173.9.3] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 07/05/2012 05:09 PM, Johannes Weiner wrote: > In the very first review iteration of AutoNUMA, Peter argued that the > scheduler people want to use this flag in other places where they rely > on this thing meaning a single cpu, not a group of them (check out the > cpumask test in debug_smp_processor_id() in lib/smp_processor_id.c). > > He also argued that preventing root from rebinding the numa daemons is > not critical to this feature at all. And I have to agree. Despite not being a scheduler expert, I'll have to side with that as well. The thing I have in mind is: We have people whose usecase depend on completely isolating cpus, with nothing but a specialized task running on it. For those people, even the hard binding between cpu0 and the timer interrupt is a big problem. If you force a per-node binding of a kthread, you are basically saying that those people are unable to isolate a node. Or else, that they have to choose between that, and AutoNUMA. Both are suboptimal choices, to say the least.