Received: by 2002:a05:6a10:a852:0:0:0:0 with SMTP id d18csp1473942pxy; Sat, 1 May 2021 15:06:24 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwXvYbjsB4kCq6Hid99b7oEYi9lnf+wd04skEKA7KKxS/hKWq9vcXGUakWq1RxxJibSgn7m X-Received: by 2002:aa7:d806:: with SMTP id v6mr13068383edq.309.1619906783919; Sat, 01 May 2021 15:06:23 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1619906783; cv=none; d=google.com; s=arc-20160816; b=0eIhhUxMRtbLx+pR9n4DMVpJDBBRRLDYwIiV55WDWuH1KmfncYBGkHg/eFkhzFvedM UGLQz8rpvjygXSqyMptKcpmNgHpxZb0Z7z6HJKE3eKm0FPHzWLC9ODTbYLCJEIoz0nJP i80FFsR5NIJLtw1GjC3k6HPzReE9x1BI43NEJSyY1AS598i0S+hSHHX2rRrfX7jVehm1 /m7nbnampMtrUpvq2FA5ANsVu7EJtJbgrn28mx2QKMYIfeKGFj5bzxtZBNZ9M/MlVL6r TtmIHFE5YY7aDPilMDszqiFYbB69ZZP/zyUnkKZpGpMQo79mSBgI+0jzCXMOQ2hW9AjH 2EWw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :user-agent:organization:references:in-reply-to:date:cc:to:from :subject:message-id:dkim-signature; bh=Js+GaB17CMiaTOtjm6gUVj7FN3DfTKpTGNOBnmvNMzg=; b=cP66a1kpmuDvYiR+EhSngP6OTRuX/JUf6wURjoQ3ZnV/Foo9Wc6G1Pux+B5305cJbE R5XkOj7wJlrwBNz6qdDXEmWzOWI6weJ/LLkVxicIL7vU73j492fPYq5IfxFHW/Dod0Kf 3xOuo/s7Ww4Rq0lTHKSXUzVK7rN/36k5iqIvN7MMJ1Jb5sAhE/FxS27dRK6McxP1Gm7w VFafGJ9lkQW7Ykc4mgvRqJQTLSrvzEobK07nNUQ4t0yCG6kA2nNRnOu9igMTrJrBxqTT O3TSC15DZG74dNjzimU7Z7zLy9vrve7sAfSqi46kBUS/s92ClmjPhkJky/Hrp3+xJ0zt 8T8w== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=YHMilZik; 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=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id v18si6154282edb.78.2021.05.01.15.06.00; Sat, 01 May 2021 15:06:23 -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=@redhat.com header.s=mimecast20190719 header.b=YHMilZik; 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=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231670AbhEAWEt (ORCPT + 99 others); Sat, 1 May 2021 18:04:49 -0400 Received: from us-smtp-delivery-124.mimecast.com ([170.10.133.124]:53156 "EHLO us-smtp-delivery-124.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229912AbhEAWEs (ORCPT ); Sat, 1 May 2021 18:04:48 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1619906638; 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: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=Js+GaB17CMiaTOtjm6gUVj7FN3DfTKpTGNOBnmvNMzg=; b=YHMilZikUgjtH21jGpnwIJvZfyiU5G8/l/M/mdwsq58tSozXsp6ak7C4IrBxmazG+yC7X1 IDQu754bu61CP8KV+F+KQn6RlaFYdamu1w7ngUTIRJghwAZQ56DIlPT0rIrNvOxWv27xwG hZtdueMPZDDbE/HlnGOnrR4AW1l0Qbs= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-604-zrr61oAkOaeaeyWmK0PJbg-1; Sat, 01 May 2021 18:03:53 -0400 X-MC-Unique: zrr61oAkOaeaeyWmK0PJbg-1 Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.phx2.redhat.com [10.5.11.15]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id BF767801B20; Sat, 1 May 2021 22:03:51 +0000 (UTC) Received: from ovpn-112-143.rdu2.redhat.com (ovpn-112-143.rdu2.redhat.com [10.10.112.143]) by smtp.corp.redhat.com (Postfix) with ESMTP id 634EB5D6AB; Sat, 1 May 2021 22:03:48 +0000 (UTC) Message-ID: <7b796a085b0bc638c9df70d3a20718f8d1d776c8.camel@redhat.com> Subject: Re: [PATCH v2 0/3] newidle_balance() PREEMPT_RT latency mitigations From: Scott Wood To: Vincent Guittot Cc: Ingo Molnar , Peter Zijlstra , Dietmar Eggemann , Steven Rostedt , Mel Gorman , Valentin Schneider , linux-kernel , linux-rt-users , Sebastian Andrzej Siewior , Thomas Gleixner Date: Sat, 01 May 2021 17:03:47 -0500 In-Reply-To: References: <20210428232821.2506201-1-swood@redhat.com> Organization: Red Hat Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.36.5 (3.36.5-2.fc32) MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.79 on 10.5.11.15 Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 2021-04-29 at 09:12 +0200, Vincent Guittot wrote: > Hi Scott, > > On Thu, 29 Apr 2021 at 01:28, Scott Wood wrote: > > These patches mitigate latency caused by newidle_balance() on large > > systems when PREEMPT_RT is enabled, by enabling interrupts when the lock > > is dropped, and exiting early at various points if an RT task is > > runnable > > on the current CPU. > > > > On a system with 128 CPUs, these patches dropped latency (as measured by > > a 12 hour rteval run) from 1045us to 317us (when applied to > > 5.12.0-rc3-rt3). > > The patch below has been queued for v5.13 and removed the update of > blocked load what seemed to be the major reason for long preempt/irq > off during newly idle balance: > https://lore.kernel.org/lkml/20210224133007.28644-1-vincent.guittot@linaro.org/ > > I would be curious to see how it impacts your cases I still get 1000+ ms latencies with those patches applied. -Scott