From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-10.5 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,INCLUDES_PATCH,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,URIBL_BLOCKED,USER_AGENT_SANE_1 autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 6A840C56201 for ; Thu, 19 Nov 2020 16:43:05 +0000 (UTC) Received: from merlin.infradead.org (merlin.infradead.org [205.233.59.134]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id E27662220B for ; Thu, 19 Nov 2020 16:43:04 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lists.infradead.org header.i=@lists.infradead.org header.b="ZGq++dSw"; dkim=fail reason="signature verification failed" (1024-bit key) header.d=kernel.org header.i=@kernel.org header.b="wdqvydQZ" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org E27662220B Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=kernel.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=merlin.20170209; h=Sender:Content-Transfer-Encoding: Content-Type:Cc:List-Subscribe:List-Help:List-Post:List-Archive: List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:References:Message-ID: Subject:To:From:Date:Reply-To:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=lHIHQtbhQnQrusjHedPoH7UXcnP10FOI7TCA9ucTvyk=; b=ZGq++dSwy/tsDSz9FPEshGwAH molZdAT8lejftzilOOxidTETX6O2DvfqgXSejB+7OWADOBrPe4zod97arvVPbJdZqfHYLBzxj5xcT MLzoMJc9BNemwLGBeylTf3+QQhksAbsJ1w75K9hISuIG8oyzfsuIl+bEGOT+7vLcpyL032QZXT9Nl fe4XxJP6SD8HOZPQeBgaVJvMZaiOogXfc4X8uwSCCLnCI96OsBi/xik8LT0RShB2Wf8hHXtKYDI1t Zy36NbAZvWI4kAOrhkHv1cN60+jKWUCqPFFFc1dsajFpwUGpVgEFL0ejhDHVyfTeFNSNayFjFzOf5 pXf/TnruQ==; Received: from localhost ([::1] helo=merlin.infradead.org) by merlin.infradead.org with esmtp (Exim 4.92.3 #3 (Red Hat Linux)) id 1kfn0E-0008B7-GM; Thu, 19 Nov 2020 16:41:46 +0000 Received: from mail.kernel.org ([198.145.29.99]) by merlin.infradead.org with esmtps (Exim 4.92.3 #3 (Red Hat Linux)) id 1kfn09-000890-CW for linux-arm-kernel@lists.infradead.org; Thu, 19 Nov 2020 16:41:43 +0000 Received: from willie-the-truck (236.31.169.217.in-addr.arpa [217.169.31.236]) (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 DA7022220B; Thu, 19 Nov 2020 16:41:36 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1605804100; bh=IdNj10e/sr3b3LdQtcOLRRg2JJyeeh5XmiDCYsVk77I=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=wdqvydQZQ26mI0gT3SQ5VKM5IhdXfEQ8VgwTBlmOBqVHfH0/KPdIOgwcdOGFzH6v1 /0MGPlofiGzxedOeEeBZz+RuTolxNUXr8TN05c8PqWwG+Y+YvjMckmsHgIOYykIGs2 mGxx0kU96+vE7hoxIFRJXZZoaaQu2VFmrUe6T4IE= Date: Thu, 19 Nov 2020 16:41:33 +0000 From: Will Deacon To: Valentin Schneider Subject: Re: [PATCH v3 07/14] sched: Introduce restrict_cpus_allowed_ptr() to limit task CPU affinity Message-ID: <20201119164133.GD4582@willie-the-truck> References: <20201113093720.21106-1-will@kernel.org> <20201113093720.21106-8-will@kernel.org> <20201119091820.GA2416649@google.com> <20201119110549.GA3946@willie-the-truck> <20201119131301.GD4331@willie-the-truck> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20201119_114141_645072_9B9F2B48 X-CRM114-Status: GOOD ( 27.69 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: linux-arch@vger.kernel.org, Juri Lelli , kernel-team@android.com, Vincent Guittot , Quentin Perret , Peter Zijlstra , Catalin Marinas , Johannes Weiner , linux-kernel@vger.kernel.org, Qais Yousef , Ingo Molnar , Li Zefan , Greg Kroah-Hartman , Marc Zyngier , Tejun Heo , Suren Baghdasaryan , Morten Rasmussen , linux-arm-kernel@lists.infradead.org Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Thu, Nov 19, 2020 at 02:54:32PM +0000, Valentin Schneider wrote: > > On 19/11/20 13:13, Will Deacon wrote: > > On Thu, Nov 19, 2020 at 11:27:55AM +0000, Valentin Schneider wrote: > >> > >> On 19/11/20 11:05, Will Deacon wrote: > >> > On Thu, Nov 19, 2020 at 09:18:20AM +0000, Quentin Perret wrote: > >> >> > @@ -1937,20 +1931,69 @@ static int __set_cpus_allowed_ptr(struct task_struct *p, > >> >> > * OK, since we're going to drop the lock immediately > >> >> > * afterwards anyway. > >> >> > */ > >> >> > - rq = move_queued_task(rq, &rf, p, dest_cpu); > >> >> > + rq = move_queued_task(rq, rf, p, dest_cpu); > >> >> > } > >> >> > out: > >> >> > - task_rq_unlock(rq, p, &rf); > >> >> > + task_rq_unlock(rq, p, rf); > >> >> > >> >> And that's a little odd to have here no? Can we move it back on the > >> >> caller's side? > >> > > >> > I don't think so, unfortunately. __set_cpus_allowed_ptr_locked() can trigger > >> > migration, so it can drop the rq lock as part of that and end up relocking a > >> > new rq, which it also unlocks before returning. Doing the unlock in the > >> > caller is therfore even weirder, because you'd have to return the lock > >> > pointer or something horrible like that. > >> > > >> > I did add a comment about this right before the function and it's an > >> > internal function to the scheduler so I think it's ok. > >> > > >> > >> An alternative here would be to add a new SCA_RESTRICT flag for > >> __set_cpus_allowed_ptr() (see migrate_disable() faff in > >> tip/sched/core). Not fond of either approaches, but the flag thing would > >> avoid this "quirk". > > > > I tried this when I read about the migrate_disable() stuff on lwn, but I > > didn't really find it any better to work with tbh. It also doesn't help > > with the locking that Quentin was mentioning, does it? (i.e. you still > > have to allocate). > > > > You could keep it all bundled within __set_cpus_allowed_ptr() (i.e. not > have a _locked() version) and use the flag as indicator of any extra work. Ah, gotcha. Still not convinced it's any better, but I see that it works. > Also FWIW we have this pattern of pre-allocating pcpu cpumasks > (select_idle_mask, load_balance_mask), but given this is AIUI a > very-not-hot path, this might be overkill (and reusing an existing one > would be on the icky side of things). I think that makes sense for static masks, but since this is dynamic I was following the lead of sched_setaffinity(). Will _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel