Received: by 2002:a25:1985:0:0:0:0:0 with SMTP id 127csp130636ybz; Thu, 16 Apr 2020 21:09:07 -0700 (PDT) X-Google-Smtp-Source: APiQypKGhVoz/NMusetMmZAzv/pkWnxquMSgD7O7CvxW6bHqvLm7WUt2SByil+GmmkdfluWS5Hvb X-Received: by 2002:a17:906:b28f:: with SMTP id q15mr1134466ejz.188.1587096547094; Thu, 16 Apr 2020 21:09:07 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1587096547; cv=none; d=google.com; s=arc-20160816; b=PCMV892p39a31JV7kU0jbLGLfEeG0CKJulvSeT1NYDzOD/zrUPije5xmiAu80xLDyM JbClMzcYIEMBgF7DpsANSvyvvMediSmorBbOQmX3cyX93Qe2tMVPpepeo931NNDhinFe /uyqKLlCq8uxDKkmKtXMkuhmswYwLh+hL12PM8IC8r2Kn+8/cbozgECANSlMg4i5u/gv gVGbks77YKm3owBcXNCTt5j0ZxqTgbb7XEHy5Ut0j/vm7PSmPHAVDgQpZ+WLBbjT9Z2j SGCcb5IgbQ1pM+83RrF949++C79VVjt+Yap9U1Tt9JkDjuc2vm+itaOB313yWreyDAp8 SahQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:message-id:subject:cc:to:from:date :dkim-signature; bh=bZnoaMSzjmrvLnW9LKkm0sdyTh3I9qRyyQKB4dlEZf4=; b=jlKNx/UtKKcP+dCy3i0vzWtaJKF+fPJDNoFtDgy22AUlb9G8FBK3hWCuKe1yadN3jr abDmiXJc2/f4LESFicOYhAR6pWPGWcMqgYabedSGdJMeqBDB4y9UIsX8ejPakRM+xoSL BNGduzV3m3PiE1TffEcoFGd8QZ+IfKT+UWFpdfqeh2Kvt6tXgY0t+4UdaLT0FHnghY+L VMA65VKjZd2ayBdLkLKmwMyURXnjd2ImKmgK9vmdCQpbeEAgkR9wZVc8r1FImau+jVY3 fgvJiFhOiJMZdQ48ZfPVJOzVf/fa637/Y4+hmCgmPWdy+20nCSvY/bA+eVMJ0bOwIK0z laGg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b="QY7ZU/+J"; 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 i63si1008549edd.601.2020.04.16.21.08.35; Thu, 16 Apr 2020 21:09:07 -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=@kernel.org header.s=default header.b="QY7ZU/+J"; 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 S1726384AbgDQEGr (ORCPT + 99 others); Fri, 17 Apr 2020 00:06:47 -0400 Received: from mail.kernel.org ([198.145.29.99]:54606 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725900AbgDQEGr (ORCPT ); Fri, 17 Apr 2020 00:06:47 -0400 Received: from localhost.localdomain (c-73-231-172-41.hsd1.ca.comcast.net [73.231.172.41]) (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 C772321D93; Fri, 17 Apr 2020 04:06:46 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1587096407; bh=Ox+92WObcJunp5pe05700XTqNPVCEcZ9XiB7PoMy0Tc=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=QY7ZU/+JVxuT2+vH/epQoI3Nw4QIVGsEgVwexZzpUIVeCl6hpubioHP9oR74gcb42 J1FpGvATJx+EGzI4rv2eMbjBISoyvIVfXOAaSaKV7uL+V6KcMVSBDwQMMtgCK4cJz1 AvgNYBimV4WNZVsQfXSLzqxwE6GXL3J2t/S1JbUI= Date: Thu, 16 Apr 2020 21:06:46 -0700 From: Andrew Morton To: "Huang\, Ying" Cc: Andrea Righi , Minchan Kim , Anchal Agarwal , , Subject: Re: [PATCH v3] mm: swap: properly update readahead statistics in unuse_pte_range() Message-Id: <20200416210646.774bae8c321e3a44d6ffa8c3@linux-foundation.org> In-Reply-To: <871romvmrh.fsf@yhuang-dev.intel.com> References: <20200416180132.GB3352@xps-13> <871romvmrh.fsf@yhuang-dev.intel.com> X-Mailer: Sylpheed 3.5.1 (GTK+ 2.24.31; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 17 Apr 2020 11:01:22 +0800 "Huang\, Ying" wrote: > Andrea Righi writes: > > > In unuse_pte_range() we blindly swap-in pages without checking if the > > swap entry is already present in the swap cache. > > > > By doing this, the hit/miss ratio used by the swap readahead heuristic > > is not properly updated and this leads to non-optimal performance during > > swapoff. > > It's more important to describe why we need this patch in the patch > description. So, please add some information about your use case. And > please focus on the technical part instead of the business part. Confused. I thought the changelog was quite good. If "business part" means "end user effect of the patch" then that's a very important thing. > Thanks! But you don't need to do this. You can add my Reviewed-by after > we have finished the work on patch description. Can you be more specific about how you want this changed?