Received: by 2002:a5b:505:0:0:0:0:0 with SMTP id o5csp1077081ybp; Fri, 4 Oct 2019 09:10:24 -0700 (PDT) X-Google-Smtp-Source: APXvYqz48NxuXI3yiT6Z70yaDdOW3ruH5GynBZRq5oVkIPXhFc4JzrPQr5PrgyzorA5yeMWjL1Pm X-Received: by 2002:a17:906:eb86:: with SMTP id mh6mr13141059ejb.171.1570205424008; Fri, 04 Oct 2019 09:10:24 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1570205423; cv=none; d=google.com; s=arc-20160816; b=MqPXQtqwXSrNk81Y+tguT/4/2jgq5O7CfGxdMVj5O4GXeS0h99bczASM0CwRdsudXh E0NruWUGBhDOAehyF1QfnN7nKrytmOM8cCJGfJTY9/cwVyus3nnVurXdu5WoEgp7VDH3 i3hesKSA+kaU/bYoBELL5byE/jLdLM/6GcvWdSzBFGpodFDWHIJIP8QR5Nm6ud5p1Fxa ycSr7H3CLNTgWJgxs8E9qNP1AWJ+dHooBOH3cMPB0Dia6U9eFAZNOT/DMhOT8zUFoVzO H1S5SLB24Wo+Ovyn3jRPi6E6xSg6AVn5X1gLHXUWq7knZz7MAuL3nrd+KfCvDjdIwfne TfzQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:message-id:date:subject:cc:to:from; bh=/DQHM2oGRfXwCPm38OnbF8APmMh0N4obEZtcQgwc/H8=; b=i2XT470OfVpwRt+GXWa2mT3KJFtj0AlaRKvHcyrs2Nuw+WD7zN19OypziPgi4HitLz cCL73mqmi0ZTotWh1BsObad51/5ZS9pGa4UT/AovcebeA8Gdt8Ub1ApAAJvPzJXSA8Hc 1d/lfYndqLJsmJ8xG0xRa/UfOuiorFKr4FzXCFr/1efS0/UIyW7dK7gmYuEaS8wZPoWP p1DXNhqgqUiPB8g1BQjr3enPWHnHG5DdlX3cIDmH0mZj9AUBndNsridkp72xJ0IB1taw QbYiwKQZ+qrw78vwYxS3hHdq9NZ75NiboMcU7AM1O8LDRa+Q6NnhMfkoGyP5kLQGxLMx k16w== 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 27si3872229edz.186.2019.10.04.09.09.58; Fri, 04 Oct 2019 09:10:23 -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 S2390239AbfJDQG4 (ORCPT + 99 others); Fri, 4 Oct 2019 12:06:56 -0400 Received: from mga12.intel.com ([192.55.52.136]:19328 "EHLO mga12.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2390140AbfJDQGz (ORCPT ); Fri, 4 Oct 2019 12:06:55 -0400 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga002.jf.intel.com ([10.7.209.21]) by fmsmga106.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 04 Oct 2019 09:06:55 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.67,256,1566889200"; d="scan'208";a="204360824" Received: from richard.sh.intel.com (HELO localhost) ([10.239.159.54]) by orsmga002.jf.intel.com with ESMTP; 04 Oct 2019 09:06:53 -0700 From: Wei Yang To: akpm@linux-foundation.org, kirill.shutemov@linux.intel.com, jglisse@redhat.com, mike.kravetz@oracle.com, riel@surriel.com, khlebnikov@yandex-team.ru Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org, Wei Yang Subject: [PATCH] mm/rmap.c: reuse mergeable anon_vma as parent when fork Date: Sat, 5 Oct 2019 00:06:32 +0800 Message-Id: <20191004160632.30251-1-richardw.yang@linux.intel.com> X-Mailer: git-send-email 2.17.1 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org In function __anon_vma_prepare(), we will try to find anon_vma if it is possible to reuse it. While on fork, the logic is different. Since commit 5beb49305251 ("mm: change anon_vma linking to fix multi-process server scalability issue"), function anon_vma_clone() tries to allocate new anon_vma for child process. But the logic here will allocate a new anon_vma for each vma, even in parent this vma is mergeable and share the same anon_vma with its sibling. This may do better for scalability issue, while it is not necessary to do so especially after interval tree is used. Commit 7a3ef208e662 ("mm: prevent endless growth of anon_vma hierarchy") tries to reuse some anon_vma by counting child anon_vma and attached vmas. While for those mergeable anon_vmas, we can just reuse it and not necessary to go through the logic. After this change, kernel build test reduces 20% anon_vma allocation. Signed-off-by: Wei Yang --- mm/rmap.c | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/mm/rmap.c b/mm/rmap.c index d9a23bb773bf..12f6c3d7fd9d 100644 --- a/mm/rmap.c +++ b/mm/rmap.c @@ -262,6 +262,17 @@ int anon_vma_clone(struct vm_area_struct *dst, struct vm_area_struct *src) { struct anon_vma_chain *avc, *pavc; struct anon_vma *root = NULL; + struct vm_area_struct *prev = dst->vm_prev, *pprev = src->vm_prev; + + /* + * If parent share anon_vma with its vm_prev, keep this sharing in in + * child. + * + * 1. Parent has vm_prev, which implies we have vm_prev. + * 2. Parent and its vm_prev have the same anon_vma. + */ + if (pprev && pprev->anon_vma == src->anon_vma) + dst->anon_vma = prev->anon_vma; list_for_each_entry_reverse(pavc, &src->anon_vma_chain, same_vma) { struct anon_vma *anon_vma; -- 2.17.1