Received: by 2002:a25:1985:0:0:0:0:0 with SMTP id 127csp589716ybz; Wed, 15 Apr 2020 14:40:12 -0700 (PDT) X-Google-Smtp-Source: APiQypLaqTWxNN4UHpD0tIKQtLv6aOkl2JX6YskBioyZhaf6HUSBm5CDeGT1VDvB+5k9AYvwoYYD X-Received: by 2002:aa7:cf07:: with SMTP id a7mr27191781edy.339.1586986812793; Wed, 15 Apr 2020 14:40:12 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1586986812; cv=none; d=google.com; s=arc-20160816; b=heOcvDlIAxWMo7ONCtoTqA7xufRECFzM/bpdkkjPOLTDHXRfLwQYdjcJL6dDAzsqde 3VBJPXnGy83pRCqa3CqV+3qEwUHZ9TVu35xS8Y3EVohRAMilocDCGVdMLejEa74g5NeF gH7XBjLZydelrR76P8dwyPdm3vIVxCEbJaIWfPh5EsWx4P3zdKdlkirtDW4CR8MuD7Na FyKgLf5cyoERIwtp7EcIr6Q0G099qjtcz4wA5fgCVc43Du1vbgTqXhQUMGFigFdjCZ6r vQsQxeIifkivHxXXnNi7IoaYsnAxGVELBPgJSa8eXrGDFHkQnaSyfaFZJ3dOH6U2Vrsm vlmA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:message-id:date:in-reply-to :subject:cc:to:from:user-agent:references; bh=pZdVVkMDL+XWae69YEhuzMgJZIH5GuAfOtZGeoqquKs=; b=xd6PtlnTL2kCw6VRTqnsqG3mncko3nNfTJNJ/72Mf+15rcRsGtd1FxcjzI/ulRs04f goCjCLieznO3PZi1sbifdXNNaG++PtQreDaNSSePfps8IuJXhlvPF8dULzuYWCrx7Ezg 7JkbWfHE7uo35GxuOvzO2NXxjsezs3xG5Z2NsG3GEUXwcETDOJ8WP6GO/f9bDSheDaPM S3Fl2uZd0bx/gBbuZO7ApKqfn8iMfkZ4yBL1a47wlS9sJsUIbizLemRNoLzv/g5GEgpZ BW0Lj77MouVFfOD6Y2NEbqlgIfNMdUQC8VA1eqhQHsFRK8j9K3TbNSPY0IyoYaEB1pWM tUrg== ARC-Authentication-Results: i=1; mx.google.com; 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id d4si863608eds.139.2020.04.15.14.39.49; Wed, 15 Apr 2020 14:40:12 -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; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2390899AbgDNO3R (ORCPT + 99 others); Tue, 14 Apr 2020 10:29:17 -0400 Received: from foss.arm.com ([217.140.110.172]:56948 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2390563AbgDNO3E (ORCPT ); Tue, 14 Apr 2020 10:29:04 -0400 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 31C7731B; Tue, 14 Apr 2020 07:29:04 -0700 (PDT) Received: from e113632-lin (e113632-lin.cambridge.arm.com [10.1.194.46]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 349573F73D; Tue, 14 Apr 2020 07:29:02 -0700 (PDT) References: <20200408095012.3819-1-dietmar.eggemann@arm.com> <20200408095012.3819-3-dietmar.eggemann@arm.com> <20200408153032.447e098d@nowhere> <31620965-e1e7-6854-ad46-8192ee4b41af@arm.com> <20200414114032.wigdlnegism6qqns@e107158-lin.cambridge.arm.com> User-agent: mu4e 0.9.17; emacs 26.3 From: Valentin Schneider To: Qais Yousef Cc: Dietmar Eggemann , luca abeni , Ingo Molnar , Peter Zijlstra , Juri Lelli , Vincent Guittot , Steven Rostedt , Daniel Bristot de Oliveira , Wei Wang , Quentin Perret , Alessio Balsini , Pavan Kondeti , Patrick Bellasi , Morten Rasmussen , linux-kernel@vger.kernel.org Subject: Re: [PATCH 2/4] sched/deadline: Improve admission control for asymmetric CPU capacities In-reply-to: <20200414114032.wigdlnegism6qqns@e107158-lin.cambridge.arm.com> Date: Tue, 14 Apr 2020 15:29:00 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 14/04/20 12:40, Qais Yousef wrote: > > I haven't followed this discussion closely, so I could be missing something > here. > > In sched_cpu_dying() we call set_rq_offline() which clears the cpu in > rq->rd->online. > > So the way I read the code > > rd->online = cpumask_and(rd->span, cpu_active_mask) > > But I could have easily missed some detail. > sched_cpu_dying() is wayyyy below sched_cpu_deactivate(). This doesn't help at all for the dl_cpu_busy() check in sched_cpu_deactivate(). > Regardless, it seems to me that DL is working around something not right in the > definition of rd->span or using the wrong variable. > What DL is doing now is fine, it only needs to be aligned with the active mask (which it is). We're making things a bit trickier by adding capacity values into the mix. > My 2p :-). I have to go back and read the discussion in more detail. > > Thanks