From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758022AbcBCWnZ (ORCPT ); Wed, 3 Feb 2016 17:43:25 -0500 Received: from mail.linuxfoundation.org ([140.211.169.12]:46449 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755479AbcBCWnS (ORCPT ); Wed, 3 Feb 2016 17:43:18 -0500 Date: Wed, 3 Feb 2016 14:43:16 -0800 From: Andrew Morton To: Dave Hansen Cc: "Kirill A. Shutemov" , Andrea Arcangeli , Hugh Dickins , Mel Gorman , Rik van Riel , Vlastimil Babka , Christoph Lameter , Naoya Horiguchi , Steve Capper , "Aneesh Kumar K.V" , Johannes Weiner , Michal Hocko , Jerome Marchand , Sasha Levin , linux-kernel@vger.kernel.org, linux-mm@kvack.org Subject: Re: [PATCH 4/4] thp: rewrite freeze_page()/unfreeze_page() with generic rmap walkers Message-Id: <20160203144316.f01573516f186071bb2cf1bf@linux-foundation.org> In-Reply-To: <56B21FC9.9040009@intel.com> References: <1454512459-94334-1-git-send-email-kirill.shutemov@linux.intel.com> <1454512459-94334-5-git-send-email-kirill.shutemov@linux.intel.com> <56B21FC9.9040009@intel.com> X-Mailer: Sylpheed 3.4.1 (GTK+ 2.24.23; 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 List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 3 Feb 2016 07:42:01 -0800 Dave Hansen wrote: > On 02/03/2016 07:14 AM, Kirill A. Shutemov wrote: > > But the new variant is somewhat slower. Current helpers iterates over > > VMAs the compound page is mapped to, and then over ptes within this VMA. > > New helpers iterates over small page, then over VMA the small page > > mapped to, and only then find relevant pte. > > The code simplification here is really attractive. Can you quantify > what the slowdown is? Is it noticeable, or would it be in the noise > during all the other stuff that happens under memory pressure? yup. And the "more testing is required" is a bit worrisome. Is this code really ready for getting pounded upon in -next?