Received: by 2002:a25:1985:0:0:0:0:0 with SMTP id 127csp3802865ybz; Mon, 20 Apr 2020 09:42:55 -0700 (PDT) X-Google-Smtp-Source: APiQypKoeHQ1ek+ARUl6RSGTwI0EM+BvB9qCwTKzKd49i9Ge1tPGPnAFwxbU9kQNNBd8QR09B2IM X-Received: by 2002:a50:81c5:: with SMTP id 63mr14770268ede.115.1587400975391; Mon, 20 Apr 2020 09:42:55 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1587400975; cv=none; d=google.com; s=arc-20160816; b=IRvh0xJjRujcRe9nGMPK+nIvlH23+jFVrv5SjxMzf6s1HzaKWZdKp5xeVzycj59yZj NWn7aLvN5YYFQ8l2j5ASoX9euK4fbgS9eqsNW+obquCSG2jSdEUW9i8D36jnRDkgt+e8 BmqhaRO07zGIvBCrNUdi7b3HiszkUy1MCAUVXw/7Gd9/hSjYrvaL5t2nfDIJ2tr2YEFI vPusc/lF7T7ajk5BxdPcjNvMnNLEfoem5UXtcAXpbNcMU1PUNCw3l42m6bpijBy3diZv uWS8zTUzQ8pcid3Fmayduk4AdHnIrOB4VAZhl6DtSUQ24BDf4O28zcn3wh5OGO3S3iNl CF/A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature; bh=c/cDlmvqU67PmfoC/g8ZNBRgKlNNglpZkMCsAIjTfP0=; b=tbklmYsktipmyeG1smiP19eFXNpWMRF8QFGJSewSyLeQy3NTPkNV6yjpLpY240WcrP DD4QL+RMRe1m+Z28ZCI68bv2QxUJCay5iOPnzZ4JTEWyVysQkGuEKBemJH9T7+naO9D0 EU4+dZpd2zItf4x2xopShpvPJuihDT2h/o0jW/Xne2dZ0JHBXQ55t8/GdIYk4jxHTrLx F9mYBQ3DUloxu36KZDfxbb8lxvYCXbG5T9I2o774aVcgIIup/SV/Jzf+CyRElhDVSgWQ UgFKweHc8LmCaUziJVnmRfWWMxSn1N0UCu/0aKFEt28iUQDN1gt2WC4heyDXm/XannGi escw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=0D8LAaLF; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id n10si832159edt.563.2020.04.20.09.42.32; Mon, 20 Apr 2020 09:42:55 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=0D8LAaLF; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726460AbgDTQeO (ORCPT + 99 others); Mon, 20 Apr 2020 12:34:14 -0400 Received: from mail.kernel.org ([198.145.29.99]:55114 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725287AbgDTQeN (ORCPT ); Mon, 20 Apr 2020 12:34:13 -0400 Received: from localhost (lfbn-ncy-1-985-231.w90-101.abo.wanadoo.fr [90.101.63.231]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id C2E2A20775; Mon, 20 Apr 2020 16:34:12 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1587400453; bh=hXdqdvStMdt0tN5I2czOifevXXjFsXK/cpNbPz7EVHw=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=0D8LAaLFzEt8AA3I7m6syrw55ULBFted7FhihglL6mxivC0E6Y5omZQfiE02trxNb KZ2CU/KKWdsasYMmjJrHS+Co2gp9EIhPNVRkoHt9Lj4PPLsM6x+oDPGwCVq3SvEPp5 yuXpncSXdm8rPrPhDSFSv06SbCTPExMnOsdsq3b8= Date: Mon, 20 Apr 2020 18:34:10 +0200 From: Frederic Weisbecker To: Li RongQing Cc: peterz@infradead.org, tglx@linutronix.de, mingo@kernel.org, srikar@linux.vnet.ibm.com, linux-kernel@vger.kernel.org Subject: Re: [PATCH] sched/isolation: allow isolcpus and nohz_full for different cpus Message-ID: <20200420163409.GB10024@lenoir> References: <1587027078-16239-1-git-send-email-lirongqing@baidu.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1587027078-16239-1-git-send-email-lirongqing@baidu.com> User-Agent: Mutt/1.9.4 (2018-02-28) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Apr 16, 2020 at 04:51:18PM +0800, Li RongQing wrote: > when both isolcpus and nohz_full are set, their cpus must be > same now, in fact isolcpus and nohz_full are not related, and > different cpus are expected for some cases, for example, some > cores for polling threads wants to isolcpus, and some cores for > dedicated threads, only nohz_full is expected > > so define two housekeeping mask to save these two configuration > separately and make cpus same only when both nohz_full and > isolcpus with nohz are passed into kernel > > fix a build error when CONFIG_CPUMASK_OFFSTACK is not configured > reported by kbuild test robot What is the usecase when you want to affine managed interrupt? Do you only want to affine IRQ or do you also want to affine every unbound work, such as kthread, workqueues, timers, etc...? In the end I would like to group the isolation features that only make sense together. So we could end up with three cpumasks, one for "domains", one for "nohz" and one for all "unbound" works. In fact "domains" should even disappear and become "unbound" + "load_balance", as that's the desired outcome of having NULL domains. I'm trying to prepare a suitable interface for all that in cpusets where we already have the load_balance part. Thanks.