From: Wei Yang <richardw.yang@linux.intel.com>
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 <richardw.yang@linux.intel.com>
Subject: [RESEND [PATCH] 2/2] mm/mmap.c: unlink vma before rb_erase
Date: Wed, 28 Aug 2019 14:06:14 +0800 [thread overview]
Message-ID: <20190828060614.19535-3-richardw.yang@linux.intel.com> (raw)
In-Reply-To: <20190828060614.19535-1-richardw.yang@linux.intel.com>
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 <richardw.yang@linux.intel.com>
---
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
next prev parent reply other threads:[~2019-08-28 6:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-28 6:06 [RESEND [PATCH] 0/2] mm/mmap.c: reduce subtree gap propagation a little Wei Yang
2019-08-28 6:06 ` [RESEND [PATCH] 1/2] mm/mmap.c: update *next* gap after itself Wei Yang
2019-08-28 6:06 ` Wei Yang [this message]
2019-08-28 8:01 ` [RESEND [PATCH] 0/2] mm/mmap.c: reduce subtree gap propagation a little Vlastimil Babka
2019-08-28 8:27 ` Wei Yang
2019-12-23 3:05 ` Wei Yang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190828060614.19535-3-richardw.yang@linux.intel.com \
--to=richardw.yang@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=vbabka@suse.cz \
--cc=yang.shi@linux.alibaba.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.