From: Balbir Singh <sblbir@amzn.com>
To: Wei Yang <richardw.yang@linux.intel.com>
Cc: <akpm@linux-foundation.org>, <mhocko@suse.com>, <vbabka@suse.cz>,
<kirill.shutemov@linux.intel.com>, <linux-mm@kvack.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mm/mmap.c: refine data locality of find_vma_prev
Date: Tue, 6 Aug 2019 10:58:22 +0000 [thread overview]
Message-ID: <20190806105822.GA25354@dev-dsk-sblbir-2a-88e651b2.us-west-2.amazon.com> (raw)
In-Reply-To: <20190806081123.22334-1-richardw.yang@linux.intel.com>
On Tue, Aug 06, 2019 at 04:11:23PM +0800, Wei Yang wrote:
> When addr is out of the range of the whole rb_tree, pprev will points to
> the biggest node. find_vma_prev gets is by going through the right most
> node of the tree.
>
> Since only the last node is the one it is looking for, it is not
> necessary to assign pprev to those middle stage nodes. By assigning
> pprev to the last node directly, it tries to improve the function
> locality a little.
>
> Signed-off-by: Wei Yang <richardw.yang@linux.intel.com>
> ---
> mm/mmap.c | 7 +++----
> 1 file changed, 3 insertions(+), 4 deletions(-)
>
> diff --git a/mm/mmap.c b/mm/mmap.c
> index 7e8c3e8ae75f..284bc7e51f9c 100644
> --- a/mm/mmap.c
> +++ b/mm/mmap.c
> @@ -2271,11 +2271,10 @@ find_vma_prev(struct mm_struct *mm, unsigned long addr,
> *pprev = vma->vm_prev;
> } else {
> struct rb_node *rb_node = mm->mm_rb.rb_node;
> - *pprev = NULL;
> - while (rb_node) {
> - *pprev = rb_entry(rb_node, struct vm_area_struct, vm_rb);
> + while (rb_node && rb_node->rb_right)
> rb_node = rb_node->rb_right;
> - }
> + *pprev = rb_node ? NULL
> + : rb_entry(rb_node, struct vm_area_struct, vm_rb);
Can rb_node ever be NULL? assuming mm->mm_rb.rb_node is not NULL when we
enter here
Balbir Singh
next prev parent reply other threads:[~2019-08-06 10:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-06 8:11 Wei Yang
2019-08-06 9:29 ` Vlastimil Babka
2019-08-07 0:31 ` Wei Yang
2019-08-07 7:51 ` Michal Hocko
2019-08-08 3:26 ` Wei Yang
2019-08-08 6:02 ` Michal Hocko
2019-08-08 8:44 ` Wei Yang
2019-08-08 8:49 ` Vlastimil Babka
2019-08-08 14:33 ` Wei Yang
2019-08-06 10:58 ` Balbir Singh [this message]
2019-08-07 0:32 ` 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=20190806105822.GA25354@dev-dsk-sblbir-2a-88e651b2.us-west-2.amazon.com \
--to=sblbir@amzn.com \
--cc=akpm@linux-foundation.org \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=richardw.yang@linux.intel.com \
--cc=vbabka@suse.cz \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox