Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id AAE00C6FD1D for ; Fri, 17 Mar 2023 18:37:35 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230103AbjCQShe (ORCPT ); Fri, 17 Mar 2023 14:37:34 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:45214 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229923AbjCQShc (ORCPT ); Fri, 17 Mar 2023 14:37:32 -0400 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 2BD264AFD6 for ; Fri, 17 Mar 2023 11:36:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1679078206; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=itVFT7T9k2vMULidRgUTx/fUeL9djtDRWADa6m3161Q=; b=Oa6kKhhig3JZEQg1CrcXPSdw4Fgjw3yc9JIJC7hoo1eHim3IvmCPsRWxyr7HQ+A9eV7b00 kfFGXl8Y4pCVifl5cuu/QvQvyH2j8nRo/ZA0rztppVvAFMQtAc0P6eNOhr/uyB+FhIZiKf fKEbvzZ8XkRWGvbp2oks1tk9JZVLLQY= Received: from mimecast-mx02.redhat.com (mx3-rdu2.redhat.com [66.187.233.73]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-515-fSPug8BEN5u2awmq6oRD9Q-1; Fri, 17 Mar 2023 14:36:41 -0400 X-MC-Unique: fSPug8BEN5u2awmq6oRD9Q-1 Received: from smtp.corp.redhat.com (int-mx04.intmail.prod.int.rdu2.redhat.com [10.11.54.4]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 50D061C12988; Fri, 17 Mar 2023 18:36:40 +0000 (UTC) Received: from tpad.localdomain (ovpn-112-2.gru2.redhat.com [10.97.112.2]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 03A662027046; Fri, 17 Mar 2023 18:36:39 +0000 (UTC) Received: by tpad.localdomain (Postfix, from userid 1000) id 66CCA403B5BB4; Fri, 17 Mar 2023 15:35:05 -0300 (-03) Date: Fri, 17 Mar 2023 15:35:05 -0300 From: Marcelo Tosatti To: Michal Hocko Cc: Andrew Morton , Leonardo Bras , Frederic Weisbecker , Peter Zijlstra , Thomas Gleixner , Johannes Weiner , Roman Gushchin , Shakeel Butt , Muchun Song , LKML , linux-mm@kvack.org, Frederic Weisbecker , Michal Hocko Subject: Re: [PATCH 1/2] sched/isolation: Add cpu_is_isolated() API Message-ID: References: <20230317134448.11082-1-mhocko@kernel.org> <20230317134448.11082-2-mhocko@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Scanned-By: MIMEDefang 3.1 on 10.11.54.4 Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Mar 17, 2023 at 03:33:13PM -0300, Marcelo Tosatti wrote: > On Fri, Mar 17, 2023 at 02:44:47PM +0100, Michal Hocko wrote: > > From: Frederic Weisbecker > > > > Provide this new API to check if a CPU has been isolated either through > > isolcpus= or nohz_full= kernel parameter. > > > > It aims at avoiding kernel load deemed to be safely spared on CPUs > > running sensitive workload that can't bear any disturbance, such as > > pcp cache draining. > > Hi Michal, > > This makes no sense to me. > > HK_TYPE_DOMAIN is set when isolcpus=domain is configured. > HK_TYPE_TICK is set when nohz_full= is configured. > > The use-cases i am aware of use either: > > isolcpus=managed_irq,... nohz_full= > OR > isolcpus=domain,managed_irq,... nohz_full= > > So what is the point of this function again? > > Perhaps it made sense along with, but now does not make sense > anymore: > > Subject: [PATCH 1/2] sched/isolation: Merge individual nohz_full features into a common housekeeping flag > > The individual isolation features turned on by nohz_full were initially > split in order for each of them to be tunable through cpusets. However > plans have changed in favour of an interface (be it cpusets or sysctl) > grouping all these features to be turned on/off altogether. Then should > the need ever arise, the interface can still be expanded to handle the > individual isolation features. > > But Michal can just use housekeeping_test_cpu(cpu, HK_TYPE_TICK) and > the convertion of nohz_full features into a common housekeeping flag > can convert that to something else later? Actually introducing cpu_is_isolated() seems fine, but it can call housekeeping_test_cpu(cpu, HK_TYPE_TICK) AFAICS.