From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752821AbbCDXvy (ORCPT ); Wed, 4 Mar 2015 18:51:54 -0500 Received: from ipmail05.adl6.internode.on.net ([150.101.137.143]:39305 "EHLO ipmail05.adl6.internode.on.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751455AbbCDXvx (ORCPT ); Wed, 4 Mar 2015 18:51:53 -0500 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: A2C1FgAFmvdUPLeDLHlagwKBLII8g32ndQEBAQEBB5hPAgIBAQKBI04BAQEBAQEFAQEBATg7hBABBTocIxAIAw4KCSUPBSUDBxoTiC7YIwEBAQcCAR8YhW6FDIE9AYMwB4MXgRQFmU+Ta4IlDQ8UgVAqMYJDAQEB Date: Thu, 5 Mar 2015 10:51:26 +1100 From: Dave Chinner To: Ingo Molnar Cc: Mel Gorman , Linus Torvalds , Andrew Morton , Matt B , Linux Kernel Mailing List , linux-mm , xfs@oss.sgi.com Subject: Re: [regression v4.0-rc1] mm: IPIs from TLB flushes causing significant performance degradation. Message-ID: <20150304235126.GB18360@dastard> References: <20150303052004.GM18360@dastard> <20150303113437.GR4251@dastard> <20150303134346.GO3087@suse.de> <20150303213353.GS4251@dastard> <20150304200046.GP3087@suse.de> <20150304230045.GZ18360@dastard> <20150304233544.GA24733@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150304233544.GA24733@gmail.com> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Mar 05, 2015 at 12:35:45AM +0100, Ingo Molnar wrote: > > * Dave Chinner wrote: > > > > After going through the series again, I did not spot why there is > > > a difference. It's functionally similar and I would hate the > > > theory that this is somehow hardware related due to the use of > > > bits it takes action on. > > > > I doubt it's hardware related - I'm testing inside a VM, [...] > > That might be significant, I doubt Mel considered KVM's interpretation > of pte details? I did actaully mention that before: | I am running a fake-numa=4 config on this test VM so it's got 4 | nodes of 4p/4GB RAM each. but I think it got snipped before Mel was cc'd. Perhaps size of the nodes is relevant, too, because the steady state phase 3 memory usage is 5-6GB when this problem first shows up, and then continues into phase 4 where memory usage grows again and peaks at ~10GB.... Cheers, Dave. -- Dave Chinner david@fromorbit.com