Received: by 2002:a25:8b12:0:0:0:0:0 with SMTP id i18csp534524ybl; Wed, 28 Aug 2019 01:29:09 -0700 (PDT) X-Google-Smtp-Source: APXvYqxevLOckZRhS4svDsOowGKBZ6JC7buwS+jIm/13lh728qGawJx8KXKUlNcZvsYdwK/HpzIq X-Received: by 2002:a63:5920:: with SMTP id n32mr2348638pgb.352.1566980949086; Wed, 28 Aug 2019 01:29:09 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1566980949; cv=none; d=google.com; s=arc-20160816; b=uSvF63tXKtMZvXNPvitwTMsd2S4rNfn88+VftVSBsVGmEW+Lyy78HgCvbjhezlzElD tUfjG+sH4Ky/j1TNBfJFwOU4wwR//RdGiLgtGceJy1ceZGSElI12Kree01ksbCqn8waD gEjGRZek6Pba9ailIzE+RtomIZwC4JzBQJGZ1uDFRFFMY97eBju2GHLBzzw27DDi69Q1 01jCM+y2/0JA+yveUNIticnzU8chcLJvtyrqhMlErFBgUbjDweTPOI1k8nYI5MAgfFCD lHAT8J48TrclUiObHz5/V90ZETuvXpCq+Xw2+LPZEH76wfjP3eAJyWggYya59JdnExEn sIZw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:reply-to:message-id :subject:cc:to:from:date; bh=tbYzEDtR86efsMJjOXAI+dst57Qi3wknp9ljDVkvp/4=; b=ZIfK+9mWnTpO3xVSsLRz5X+IzMVW1Q+u8DdR0pFTXZZB3OcXTqrsRMvyYU9wwnZvDu AfrktNw8mgWhjFvZUfciOxDM/bsOgsBVEmvz/kujoFrhWFFuoiiGuuHXOe5WjB4wbssk RQ6OaXR8iyOgVi0rDVRjBuynlwrIVODzP3cmqkbwJ03UOZySpt7z8NoeaqvxjIFbnNMo LRYBr7lwSzKreVD9NbLAKU6MZCYKLhmyDnIJNmjHqDxriVx+nksQ9mGKEJQyVoyrxePj 0zk98EJTvem4Ga3tcKQbw8F7BwUZm1JomYILr0anVYHupV+HYjimzsbTJ9i2IlN4DzZy wdLA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id g6si1583225pgl.30.2019.08.28.01.28.53; Wed, 28 Aug 2019 01:29:09 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726432AbfH1I2C (ORCPT + 99 others); Wed, 28 Aug 2019 04:28:02 -0400 Received: from mga12.intel.com ([192.55.52.136]:33769 "EHLO mga12.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726253AbfH1I2C (ORCPT ); Wed, 28 Aug 2019 04:28:02 -0400 X-Amp-Result: UNKNOWN X-Amp-Original-Verdict: FILE UNKNOWN X-Amp-File-Uploaded: False Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by fmsmga106.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 28 Aug 2019 01:28:01 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.64,440,1559545200"; d="scan'208";a="210081623" Received: from richard.sh.intel.com (HELO localhost) ([10.239.159.54]) by fmsmga002.fm.intel.com with ESMTP; 28 Aug 2019 01:28:00 -0700 Date: Wed, 28 Aug 2019 16:27:38 +0800 From: Wei Yang To: Vlastimil Babka Cc: Wei Yang , akpm@linux-foundation.org, kirill.shutemov@linux.intel.com, yang.shi@linux.alibaba.com, linux-mm@kvack.org, linux-kernel@vger.kernel.org, Matthew Wilcox Subject: Re: [RESEND [PATCH] 0/2] mm/mmap.c: reduce subtree gap propagation a little Message-ID: <20190828082738.GA20183@richard> Reply-To: Wei Yang References: <20190828060614.19535-1-richardw.yang@linux.intel.com> <4503e006-76ba-ed06-0184-6e361a66ba88@suse.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4503e006-76ba-ed06-0184-6e361a66ba88@suse.cz> User-Agent: Mutt/1.9.4 (2018-02-28) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Aug 28, 2019 at 10:01:40AM +0200, Vlastimil Babka wrote: >On 8/28/19 8:06 AM, Wei Yang wrote: >> When insert and delete a vma, it will compute and propagate related subtree >> gap. After some investigation, we can reduce subtree gap propagation a little. >> >> [1]: This one reduce the propagation by update *next* gap after itself, since >> *next* must be a parent in this case. >> [2]: This one achieve this by unlinking vma from list. >> >> After applying these two patches, test shows it reduce 0.3% function call for >> vma_compute_subtree_gap. > >BTW, what's the overall motivation of focusing so much >micro-optimization effort on the vma tree lately? This has been rather >stable code where we can be reasonably sure of all bugs being found. Now >even after some review effort, subtle bugs can be introduced. And >Matthew was warning for a while about an upcoming major rewrite of the >whole data structure, which will undo all this effort? > Hi, Vlastimil Thanks for your comment. I just found there could be some refine for the code and then I modify and test it. Hope this could help a little. You concern is valid. The benefits / cost may be not that impressive. The community have the final decision. For me, I just want to make it better if we can. -- Wei Yang Help you, Help me