Received: by 2002:ac0:a5b6:0:0:0:0:0 with SMTP id m51-v6csp766391imm; Wed, 6 Jun 2018 05:46:53 -0700 (PDT) X-Google-Smtp-Source: ADUXVKJE00CLY6Sun/D3xqCDWnknOnC+MWHRehptc37p0Bdg8Q+8DGBh5suxSm5ozHEAhsHWkHnf X-Received: by 2002:a17:902:b28c:: with SMTP id u12-v6mr3140792plr.68.1528289213704; Wed, 06 Jun 2018 05:46:53 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1528289213; cv=none; d=google.com; s=arc-20160816; b=RYU7/iMzCHrJbyn9TZkHcC3RNhQou0EkQ7zsqtzzOio/KpJnQh9xRVL+hFkNc2zTSj h22nUZVRZsxD4NnV+WAf1zM91vzhA7zFCKPQLuze3FJGvUQle/DHW2YLlWZQ4tq8djKZ yHIWvyZU+o9EfNCztpFh/iSpKWetsrv1FShLy6qKZqalMt5KUpFlD4gPQ4hHmDu9jLJp 7/m4SV6uVOtp70gBe4c3/0xQoCeEmXkyb57z3xBJgPbum0nHG4SwxMwco8HXPV1Hmm3B NBfrkrnYQGsU2cVifZaNZf8AiG8kgDLSZKB6IS4Hv6j8J00nHbjZGGKYxEnJ9KP5+U4Y aXTA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :references:in-reply-to:mime-version:dkim-signature :arc-authentication-results; bh=v5AHSoLMIwTrUDvymUlgB/t8Y7/wuQq8p9WY6LmpIF0=; b=tjjxuiYIBU9deG9qZXmeo5xglJ+UYDNqZw1ryn8HcNFuZoAesGgLx/EPTttGmA9bDz k+ZjGrHCo2cpExo3FyF0Y0G3tGyoWvH/TqTNv4P8Oj9YTiUagBuHV2WyICSiS9Y8v3Gk viqAJsHnKk0ZI2URSsdmqRnJZeHC08tmMeS+S+bxS/n/qlKzvGV8e/b4w4D7bjhoeu/n bXXfmxlW2jU24X6KCm3qS8034jktFpnJ2V+PccD+M8LEBd3hwDEPdHdNUcSB6CciK9Ll YoS5fx7BikV2hAr/nJy/x/RcnSBqz1WDBMWXhj/6RZI0CBWv0k6VokQACrFuqKNJzmhO S2qA== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@gmail.com header.s=20161025 header.b=i9/5SVqc; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id r17-v6si24756153pfg.305.2018.06.06.05.46.39; Wed, 06 Jun 2018 05:46:53 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=fail header.i=@gmail.com header.s=20161025 header.b=i9/5SVqc; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752369AbeFFMo2 (ORCPT + 99 others); Wed, 6 Jun 2018 08:44:28 -0400 Received: from mail-ot0-f194.google.com ([74.125.82.194]:43371 "EHLO mail-ot0-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752016AbeFFMo0 (ORCPT ); Wed, 6 Jun 2018 08:44:26 -0400 Received: by mail-ot0-f194.google.com with SMTP id i19-v6so7190263otk.10; Wed, 06 Jun 2018 05:44:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=v5AHSoLMIwTrUDvymUlgB/t8Y7/wuQq8p9WY6LmpIF0=; b=i9/5SVqcyAAh4eoJKLPlKsMqd+elfGgKXgwtTK2qs9AInFr1I5m4rzt/FA3AWOQAu7 EL7pixZyZq5RI+kCR6s7MNc3dlyhNMdGdBFL6FMmbyZYglvUZvPQ9gByMZRRC09ca0h6 wJpuJuPi2tutdaiuqTgAVwMJTOtW41nAiK7mt8onO1BKWBKHX5UYkgRykB16rSE23jAS fEwwogsn+BmYdaRiwGzGXJEJ6pIyGEtQWdn61slmBreKqi3tRrp6hw4bHvflrE0eBR4L LCjVlOJHl5gl40feozGN2wib9zzcOE2qtpLuXq7SfNK1K7r10CYzHfTvKd4b3l7WHLhl mpig== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=v5AHSoLMIwTrUDvymUlgB/t8Y7/wuQq8p9WY6LmpIF0=; b=GBFh+62ZJFmW05ePPWYGicPqk26TobhWAX43Az84buHt3Tcmc28lCb9Uh/KCNkyq0q ElaXlidDjlDUBVNMmVuLxnTDu7AuxQvC8Kdt2LDlEDfRVhygMdBdLxB/56tZE57hEqrZ 0cHAwWz0F2MaxYJG639iolHQsvCoui+IETnFE8eFV+FifHCgdevIdp5kwxKxjvjqW/QT +EfQ2B31CkLqbvbbU6fbkqDOiq80qDKkikxhUpDqssXIwPxYtj8Y0gWoRlwPYeT8svhw 4NYO8UqpBYo2DP82n1R/+OhywGIujEiOxY1w9ZU8B2pn5naDGAFKVd5+PhU9e1OJQc/R trbA== X-Gm-Message-State: APt69E3OK5NnYfSLBZumfJ+uk5/VdjPE3qD+248hjWEnf83G4ips/7fU 800S+rZyt/tuD6DptbT0ZQHyWFbcyajni2ciS/E= X-Received: by 2002:a9d:cc7:: with SMTP id o7-v6mr1704024otd.291.1528289065752; Wed, 06 Jun 2018 05:44:25 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a9d:1468:0:0:0:0:0 with HTTP; Wed, 6 Jun 2018 05:44:25 -0700 (PDT) In-Reply-To: References: <20180606122731.GB27707@jra-laptop.brq.redhat.com> From: "Rafael J. Wysocki" Date: Wed, 6 Jun 2018 14:44:25 +0200 X-Google-Sender-Auth: hpVfNQC4mNaHqOIQE9M2c522lfI Message-ID: Subject: Re: [4.17 regression] Performance drop on kernel-4.17 visible on Stream, Linpack and NAS parallel benchmarks To: "Rafael J. Wysocki" Cc: Jakub Racek , Linux Kernel Mailing List , "Rafael J. Wysocki" , Len Brown , ACPI Devel Maling List , Peter Zijlstra Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Jun 6, 2018 at 2:34 PM, Rafael J. Wysocki wrote: > On Wed, Jun 6, 2018 at 2:27 PM, Jakub Racek wrote: >> Hi, >> >> There is a huge performance regression on the 2 and 4 NUMA node systems on >> stream benchmark with 4.17 kernel compared to 4.16 kernel. Stream, Linpack >> and NAS parallel benchmarks show upto 50% performance drop. >> >> When running for example 20 stream processes in parallel, we see the >> following behavior: >> >> * all processes are started at NODE #1 >> * memory is also allocated on NODE #1 >> * roughly half of the processes are moved to the NODE #0 very quickly. * >> however, memory is not moved to NODE #0 and stays allocated on NODE #1 >> >> As the result, half of the processes are running on NODE#0 with memory being >> still allocated on NODE#1. This leads to non-local memory accesses >> on the high Remote-To-Local Memory Access Ratio on the numatop charts. >> So it seems that 4.17 is not doing a good job to move the memory to the >> right NUMA >> node after the process has been moved. >> >> ----8<---- >> >> The above is an excerpt from performance testing on 4.16 and 4.17 kernels. >> >> For now I'm merely making sure the problem is reported. > > OK, and why do you think that it is related to ACPI? In any case, we need more information here. Thanks, Rafael