Received: by 2002:a25:8b12:0:0:0:0:0 with SMTP id i18csp414350ybl; Tue, 27 Aug 2019 23:09:24 -0700 (PDT) X-Google-Smtp-Source: APXvYqwNH56gJ934Bm5NVGeAV88z2ChrRFB3IHkD3bdvs8acXlNCPeogPkom02JwVK0/pOfHT1w1 X-Received: by 2002:a17:90a:3321:: with SMTP id m30mr2621198pjb.2.1566972564902; Tue, 27 Aug 2019 23:09:24 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1566972564; cv=none; d=google.com; s=arc-20160816; b=k5l50lw5TscqvGvqZ566Ky8l3nq7hEe8anenVWB0+F2T7CegvKUS8Qurj0kqhqaHeU Pw5Y+wS/8lnQ2s4jToEc1JRzkOUpOh2a+Tga7zY2PiF+q06iD4+7gzzdaCRiqqGs+dI/ IQ+UFC6yOT+ClgcJ5ry46vmS0bkzCrAROzT+QHWMtbL/wkbH249EKUEMbCfxdUNgKy5s l7Wl4fugITdcmq59FLjO46OzUyc4eOwddjWKtrHWLY23DSkuojA6Vb3KTr+2o6Klp1ty eLQXXO4NxYRVk0ifVjImZLWrTaqmKcxVCTonNT9VIgCh2EohMF9saphrd+rNOk2LS0Y0 JNFA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:references:in-reply-to:message-id:date :subject:cc:to:from; bh=LwL5DvI4zsVu6WDukjsb3UtxGHnJPH2wAEoxZ+EdOxE=; b=UUD2bke0R9W4nKlRsar+dyfgMuXOrxFNQ+FmefqfMaw6BEHHHGXSwm7kc07lX0cujI GK0r1nruA1bxsm1dYW9AsMusYEuhiuKByB1+CrBpuY05+E1nb+XSrCtzf9fSSRckXUx1 ibunz2pNoXPfKu6/OVK11b9caq//49oJYxbxJJovqn4JWotRfpxcx30IhYBH4eKqqIq2 l9Q+xt2GA27YYLQH6yZnmHX70MdoQW2iRWXzMGcp3fmKTIIyqna7Ru1JL+YdWL+OjO3M e657+o+BHgM7J7aK2cw+AEAXHdpierpz3/mgKfnCW/cuzthz/QeXjiS1vrf8jMb82R8D lBGw== 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 r7si1092211pli.94.2019.08.27.23.09.09; Tue, 27 Aug 2019 23:09:24 -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 S1726321AbfH1GGo (ORCPT + 99 others); Wed, 28 Aug 2019 02:06:44 -0400 Received: from mga04.intel.com ([192.55.52.120]:22063 "EHLO mga04.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726100AbfH1GGo (ORCPT ); Wed, 28 Aug 2019 02:06:44 -0400 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga006.jf.intel.com ([10.7.209.51]) by fmsmga104.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 27 Aug 2019 23:06:43 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.64,440,1559545200"; d="scan'208";a="185518935" Received: from richard.sh.intel.com (HELO localhost) ([10.239.159.54]) by orsmga006.jf.intel.com with ESMTP; 27 Aug 2019 23:06:42 -0700 From: Wei Yang To: akpm@linux-foundation.org, vbabka@suse.cz, kirill.shutemov@linux.intel.com, yang.shi@linux.alibaba.com Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org, Wei Yang Subject: [RESEND [PATCH] 2/2] mm/mmap.c: unlink vma before rb_erase Date: Wed, 28 Aug 2019 14:06:14 +0800 Message-Id: <20190828060614.19535-3-richardw.yang@linux.intel.com> X-Mailer: git-send-email 2.17.1 In-Reply-To: <20190828060614.19535-1-richardw.yang@linux.intel.com> References: <20190828060614.19535-1-richardw.yang@linux.intel.com> Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Current sequence to remove a vma is: vma_rb_erase_ignore() __vma_unlink_list() vma_gap_update() This may do some extra subtree_gap propagation due the vma is unlink from list after rb_erase. For example, we have a tree: a [0x9000, 0x10000] / \ b c [0x8000, 0x9000] [0x10000, 0x11000] / d [0x6000, 0x7000] The gap for each node is: a's gap = 0x6000 b's gap = 0x6000 c's gap = 0x0 d's gap = 0x6000 Now we want to remove node d. Since we don't unlink d from link when doing rb_erase, b's gap would still be computed to 0x1000. This leads to the vma_gap_update() after list unlink would recompute b and a's gap. For this case, by unlink the list before rb_erase, we would have one time less of vma_compute_subtree_gap. Signed-off-by: Wei Yang --- mm/mmap.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/mm/mmap.c b/mm/mmap.c index 672ad7dc6b3c..907939690a30 100644 --- a/mm/mmap.c +++ b/mm/mmap.c @@ -678,8 +678,8 @@ static __always_inline void __vma_unlink_common(struct mm_struct *mm, struct vm_area_struct *vma, struct vm_area_struct *ignore) { - vma_rb_erase_ignore(vma, &mm->mm_rb, ignore); __vma_unlink_list(mm, vma); + vma_rb_erase_ignore(vma, &mm->mm_rb, ignore); /* Kill the cache */ vmacache_invalidate(mm); } -- 2.17.1