Received: by 2002:a25:8b12:0:0:0:0:0 with SMTP id i18csp3811260ybl; Mon, 26 Aug 2019 00:33:01 -0700 (PDT) X-Google-Smtp-Source: APXvYqwS1HeGyUvSNUvxONeNh8bE5q8oSzwadWrspQw816cQJ5Rl7r+A14rynAMlCJInEzCn5OQ5 X-Received: by 2002:a62:1ad4:: with SMTP id a203mr18264860pfa.210.1566804781592; Mon, 26 Aug 2019 00:33:01 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1566804781; cv=none; d=google.com; s=arc-20160816; b=jxtE4qlDaK3tpA9bZ0cHruZQJmChTfdFxuUTq07kHz7UcGuJwFOAwjGVRWot50jFOP qmg1Eh1dh/UXo6yOSKYZYNaWcXCRFYtIlaqTY/CKd0nyjntg+seILDwFHYeI8aFnJ3QS pJ/BCFbrNkSbnzDZvvwF8CJ+Xeqg3YjAMnx3T1S6SrJSU/IhAmIUkdEus3DebXmH69rl llbOIjXQwGEaHckNQ3DjGR4VcaotNHwaW3MkfNY5618e9fsm+jEMxk6lWwMWm7R7zF28 a3nYKCrukTYczLqaI6+yxiu8P5Bq2oRuCZdkZ+dF+crw8vNvmJefC7mDY2fYxelNw4hX 2QCw== 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=ASsUmEL5OGasaf4OsEzO+EMJGRHBO5xm7vpGAeprwHvpqHmONN0bI3YmzJVgKSOLDN DUyomHzIhnBHfph9ZLv7dyAUX69Rcq+kgD6yl1BOkrwrj3VR8nUVlWCqoTcEODoB/Oc4 g945cpAzhtzV6oBPfSn+S9pS02U3hOXzjlTG/j0aOdBrCtEuHLbtN9VWJA8PKV9v/KaS jU3OQdV0fqYbExRD/V56ayDwddU4tU+6Sk3kSP9qfmJ5mkLVdl4huG+fp3TKO38035jr clj6ltlN7BMXeeTSptf0MC5NM3R1Q0ufC5nLqOU8Tfh8sMirBeobJySQrBq8OcXwevUE MeOw== 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 w4si8862947pjr.76.2019.08.26.00.32.46; Mon, 26 Aug 2019 00:33:01 -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 S1730157AbfHZHbs (ORCPT + 99 others); Mon, 26 Aug 2019 03:31:48 -0400 Received: from mga04.intel.com ([192.55.52.120]:47284 "EHLO mga04.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726896AbfHZHbq (ORCPT ); Mon, 26 Aug 2019 03:31:46 -0400 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by fmsmga104.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 26 Aug 2019 00:31:46 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.64,431,1559545200"; d="scan'208";a="196992431" Received: from richard.sh.intel.com (HELO localhost) ([10.239.159.54]) by fmsmga001.fm.intel.com with ESMTP; 26 Aug 2019 00:31:44 -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: [PATCH 2/2] mm/mmap.c: unlink vma before rb_erase Date: Mon, 26 Aug 2019 15:31:06 +0800 Message-Id: <20190826073106.29971-3-richardw.yang@linux.intel.com> X-Mailer: git-send-email 2.17.1 In-Reply-To: <20190826073106.29971-1-richardw.yang@linux.intel.com> References: <20190826073106.29971-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