Received: by 2002:ac0:a5b6:0:0:0:0:0 with SMTP id m51-v6csp3113687imm; Tue, 29 May 2018 00:58:54 -0700 (PDT) X-Google-Smtp-Source: AB8JxZpQHTyh/1qJvSepFzUEFQW5LdrQ7TSLHxMbafQ846TSX1lk7FA1hpKLpiokHbBn7yAsjZVA X-Received: by 2002:a17:902:d807:: with SMTP id a7-v6mr16354916plz.92.1527580734610; Tue, 29 May 2018 00:58:54 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1527580734; cv=none; d=google.com; s=arc-20160816; b=bxs1pDDqUAl0GxM23KZtXHdxZ5a3XmfFZKpM351qPAMRiM/H5rnCnOpMgroXj3p7Gr Jc1DcWt5IF+3QhnlnxeBMVmw6GjRntKrdlQUv5h6zICUX6/q2FsJ7hz9+fgoGW4ybpqS 9tZnsDQg6Jkm+Eh3d6eYDQWw0PoZke6g1Y670Fy2+kOKWPm9U2LFgHr86vFS18tnm1Fe ezPJx619h5slCbkk8i2uhk4E74O5nK11rxf/zfOC7OK1PAR3PihF+qxZaXVvz2/LPErD koLbow+fUKsrzJw0mwKHil90rx5/QLORyCR48B/hMi/xsXoIfcFe6izhvpMzynS0DSzU x9mQ== 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:arc-authentication-results; bh=XujhgJpg4sA4CyO7wJib8L3m+vbdNUSPcB5ftqv1yoI=; b=QnQ+pzmy6s+qQtdSsP5NQHmAg1hG11gY3+N3GxEervaX9lt0vTUGrrN6BvSp26eUi3 u+Wl2RX1/W1jgvtFoSwu/K+wL3jLgjHkr9O84wtA/4IWgtD2wW1GRMdeoT2lBFrj01p7 RuRWebAXMxEg/pNInBvoo6UPOQrwZAUn/vXcQBM6PfI2LowD5kvQd2IGObOtVfdu4+/E lYErtKww8RT4aGaOu47egPwGdIKjtE4Qwh+K5AveHVpGbQdR8Y9ziebi+HQOLb0U6cn5 dY0ylItE6AdZkZFz1iC7keZDcuunK4togJJWqIR0nV9QO/g5YQdTsDn+8B8v8+/f0V5A ZLQQ== ARC-Authentication-Results: i=1; mx.google.com; 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 x25-v6si33545307pfj.347.2018.05.29.00.58.40; Tue, 29 May 2018 00:58:54 -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; 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 S1755225AbeE2H6E (ORCPT + 99 others); Tue, 29 May 2018 03:58:04 -0400 Received: from mx2.suse.de ([195.135.220.15]:43079 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755183AbeE2H6D (ORCPT ); Tue, 29 May 2018 03:58:03 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (charybdis-ext-too.suse.de [195.135.220.254]) by mx2.suse.de (Postfix) with ESMTP id C88C5AE65; Tue, 29 May 2018 07:58:01 +0000 (UTC) Date: Tue, 29 May 2018 09:58:00 +0200 From: Michal Hocko To: "Lu, Aaron" Cc: "Ye, Xiaolong" , "tj@kernel.org" , "linux-kernel@vger.kernel.org" , "lkp@01.org" , "hannes@cmpxchg.org" Subject: Re: [LKP] [lkp-robot] [mm, memcontrol] 309fe96bfc: vm-scalability.throughput +23.0% improvement Message-ID: <20180529075800.GL27180@dhcp22.suse.cz> References: <20180528114019.GF9904@yexl-desktop> <20180528120318.GB27180@dhcp22.suse.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.5 (2018-04-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue 29-05-18 03:15:51, Lu, Aaron wrote: > On Mon, 2018-05-28 at 14:03 +0200, Michal Hocko wrote: > > On Mon 28-05-18 19:40:19, kernel test robot wrote: > > > > > > Greeting, > > > > > > FYI, we noticed a +23.0% improvement of vm-scalability.throughput due to commit: > > > > > > > > > commit: 309fe96bfc0ae387f53612927a8f0dc3eb056efd ("mm, memcontrol: implement memory.swap.events") > > > https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master > > > > This doesn't make any sense to me. The patch merely adds an accounting. > > It doesn't optimize anything. So I strongly suspect the result is just > > misleading or the test (environment) misconfigured. Not the first time > > I am seeing something like that I am afraid. > > > > Most likely the same situation as: > " > FYI, we noticed a -27.2% regression of will-it-scale.per_process_ops > due to commit: > > > commit: e27be240df53f1a20c659168e722b5d9f16cc7f4 ("mm: memcg: make sure > memory.events is uptodate when waking pollers") > https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master > " > > Where the performance change is due to layout change of > 'struct mem_cgroup': > http://lkml.kernel.org/r/20180528085201.GA2918@intel.com I do not follow. How can _this_ patch lead to an improvement when it actually _adds_ an accounting? The other report you are mentioning is a _regression_ and I can imagine that the layout changes can lead to that result. -- Michal Hocko SUSE Labs