Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751831AbdFIRAI (ORCPT ); Fri, 9 Jun 2017 13:00:08 -0400 Received: from mga01.intel.com ([192.55.52.88]:24076 "EHLO mga01.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751751AbdFIRAH (ORCPT ); Fri, 9 Jun 2017 13:00:07 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.39,317,1493708400"; d="scan'208";a="113005640" Subject: Re: [RFC v4 00/20] Speculative page faults To: Michal Hocko , Laurent Dufour Cc: paulmck@linux.vnet.ibm.com, peterz@infradead.org, akpm@linux-foundation.org, kirill@shutemov.name, ak@linux.intel.com, dave@stgolabs.net, jack@suse.cz, Matthew Wilcox , linux-kernel@vger.kernel.org, linux-mm@kvack.org, haren@linux.vnet.ibm.com, khandual@linux.vnet.ibm.com, npiggin@gmail.com, bsingharora@gmail.com References: <1497018069-17790-1-git-send-email-ldufour@linux.vnet.ibm.com> <20170609150126.GI21764@dhcp22.suse.cz> <83cf1566-3e76-d3fa-10a8-d83bbf9fd568@linux.vnet.ibm.com> <20170609163520.GB9332@dhcp22.suse.cz> From: Tim Chen Message-ID: <84e1698a-c85f-ee10-d367-2c203c6eea73@linux.intel.com> Date: Fri, 9 Jun 2017 09:59:50 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.1.0 MIME-Version: 1.0 In-Reply-To: <20170609163520.GB9332@dhcp22.suse.cz> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1102 Lines: 31 On 06/09/2017 09:35 AM, Michal Hocko wrote: > On Fri 09-06-17 17:25:51, Laurent Dufour wrote: > [...] >> Thanks Michal for your feedback. >> >> I mostly focused on this database workload since this is the one where >> we hit the mmap_sem bottleneck when running on big node. On my usual >> victim node, I checked for basic usage like kernel build time, but I >> agree that's clearly not enough. >> >> I try to find details about the 'kbench' you mentioned, but I didn't get >> any valid entry. >> Would you please point me on this or any other bench tool you think will >> be useful here ? > > Sorry I meant kernbech (aka parallel kernel build). Other highly threaded > workloads doing a lot of page faults and address space modification > would be good to see as well. I wish I could give you much more > comprehensive list but I am not very good at benchmarks. > Laurent, Have you tried running the multi-fault microbenchmark by Kamezawa? It does threaded page faults in parallel. Peter ran that when he posted his specualtive page faults patches. https://lkml.org/lkml/2010/1/6/28 Thanks. Tim