From: Peter Zijlstra <peterz@infradead.org>
To: "Luiz Fernando N. Capitulino" <lcapitulino@mandriva.com.br>
Cc: akpm@linux-foundation.org, riel@redhat.com, mingo@elte.hu,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: PATCH: Introduce struct vma_link_info
Date: Fri, 20 Mar 2009 21:36:29 +0100 [thread overview]
Message-ID: <1237581389.4667.130.camel@laptop> (raw)
In-Reply-To: <20090320103438.08e67358@doriath.conectiva>
On Fri, 2009-03-20 at 10:34 -0300, Luiz Fernando N. Capitulino wrote:
> Andrew,
>
> Currently find_vma_prepare() and low-level VMA functions (eg. __vma_link())
> require callers to provide three parameters to return/pass "link" information
> (pprev, rb_link and rb_parent):
>
> static struct vm_area_struct *
> find_vma_prepare(struct mm_struct *mm, unsigned long addr,
> struct vm_area_struct **pprev, struct rb_node ***rb_link,
> struct rb_node ** rb_parent);
>
> With this patch callers can pass a struct vma_link_info instead:
>
> static struct vm_area_struct *
> find_vma_prepare(struct mm_struct *mm, unsigned long addr,
> struct vma_link_info *link_info);
>
> The code gets simpler and it should be better because less variables
> are pushed into the stack/registers. As shown by the following
> kernel build test:
>
> kernel real user sys
>
> 2.6.29-rc8-vanilla 1136.64 1033.38 82.88
> 2.6.29-rc8-linfo 1135.07 1032.44 82.92
>
> I have also ran hackbench, but I can't understand why its result
> indicates a regression:
>
> kernel Avarage of three runs (25 processes groups)
>
> 2.6.29.rc8-vanilla 2.03
> 2.6.29.rc8-linfo 2.12
>
> Rik has said to me that this could be inside error margin. So, I'm
> submitting the patch for inclusion.
>
> Signed-off-by: Luiz Fernando N. Capitulino <lcapitulino@mandriva.com.br>
I'd rather we look into using the threaded RB-tree to get rid of all
this prev crap.
WARNING: multiple messages have this Message-ID (diff)
From: Peter Zijlstra <peterz@infradead.org>
To: "Luiz Fernando N. Capitulino" <lcapitulino@mandriva.com.br>
Cc: akpm@linux-foundation.org, riel@redhat.com, mingo@elte.hu,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: PATCH: Introduce struct vma_link_info
Date: Fri, 20 Mar 2009 21:36:29 +0100 [thread overview]
Message-ID: <1237581389.4667.130.camel@laptop> (raw)
In-Reply-To: <20090320103438.08e67358@doriath.conectiva>
On Fri, 2009-03-20 at 10:34 -0300, Luiz Fernando N. Capitulino wrote:
> Andrew,
>
> Currently find_vma_prepare() and low-level VMA functions (eg. __vma_link())
> require callers to provide three parameters to return/pass "link" information
> (pprev, rb_link and rb_parent):
>
> static struct vm_area_struct *
> find_vma_prepare(struct mm_struct *mm, unsigned long addr,
> struct vm_area_struct **pprev, struct rb_node ***rb_link,
> struct rb_node ** rb_parent);
>
> With this patch callers can pass a struct vma_link_info instead:
>
> static struct vm_area_struct *
> find_vma_prepare(struct mm_struct *mm, unsigned long addr,
> struct vma_link_info *link_info);
>
> The code gets simpler and it should be better because less variables
> are pushed into the stack/registers. As shown by the following
> kernel build test:
>
> kernel real user sys
>
> 2.6.29-rc8-vanilla 1136.64 1033.38 82.88
> 2.6.29-rc8-linfo 1135.07 1032.44 82.92
>
> I have also ran hackbench, but I can't understand why its result
> indicates a regression:
>
> kernel Avarage of three runs (25 processes groups)
>
> 2.6.29.rc8-vanilla 2.03
> 2.6.29.rc8-linfo 2.12
>
> Rik has said to me that this could be inside error margin. So, I'm
> submitting the patch for inclusion.
>
> Signed-off-by: Luiz Fernando N. Capitulino <lcapitulino@mandriva.com.br>
I'd rather we look into using the threaded RB-tree to get rid of all
this prev crap.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2009-03-20 20:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-20 13:34 PATCH: Introduce struct vma_link_info Luiz Fernando N. Capitulino
2009-03-20 13:34 ` Luiz Fernando N. Capitulino
2009-03-20 20:36 ` Peter Zijlstra [this message]
2009-03-20 20:36 ` Peter Zijlstra
2009-03-23 13:35 ` Luiz Fernando N. Capitulino
2009-03-23 13:35 ` Luiz Fernando N. Capitulino
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=1237581389.4667.130.camel@laptop \
--to=peterz@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=lcapitulino@mandriva.com.br \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@elte.hu \
--cc=riel@redhat.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.