From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758241AbcBCWxT (ORCPT ); Wed, 3 Feb 2016 17:53:19 -0500 Received: from mga02.intel.com ([134.134.136.20]:16494 "EHLO mga02.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756556AbcBCWxL (ORCPT ); Wed, 3 Feb 2016 17:53:11 -0500 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.22,392,1449561600"; d="scan'208";a="905044410" Date: Thu, 4 Feb 2016 01:53:04 +0300 From: "Kirill A. Shutemov" To: Andrew Morton Cc: Dave Hansen , 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: <20160203225304.GB22605@black.fi.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> <20160203144316.f01573516f186071bb2cf1bf@linux-foundation.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160203144316.f01573516f186071bb2cf1bf@linux-foundation.org> User-Agent: Mutt/1.5.23.1 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Feb 03, 2016 at 02:43:16PM -0800, Andrew Morton wrote: > 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. It is not really clear, how to quantify this properly. Let me think more about it. > And the "more testing is required" is a bit worrisome. Is this > code really ready for getting pounded upon in -next? By now it survived 5+ hours of fuzzing in 16 VM in parallel. I'll continue with other tests tomorrow. -- Kirill A. Shutemov