From: Andrea Arcangeli <andrea@suse.de>
To: Ben LaHaise <bcrl@redhat.com>
Cc: torvalds@transmeta.com, alan@redhat.com, linux-mm@kvack.org,
Chris Blizzard <blizzard@redhat.com>
Subject: Re: resend Re: [PATCH] final merging patch -- significant mozilla speedup.
Date: Sun, 19 Aug 2001 02:35:48 +0200 [thread overview]
Message-ID: <20010819023548.P1719@athlon.random> (raw)
In-Reply-To: <Pine.LNX.4.33.0108182005590.3026-100000@touchme.toronto.redhat.com>; from bcrl@redhat.com on Sat, Aug 18, 2001 at 08:10:50PM -0400
On Sat, Aug 18, 2001 at 08:10:50PM -0400, Ben LaHaise wrote:
> On Sun, 19 Aug 2001, Andrea Arcangeli wrote:
>
> > This below patch besides rewriting the vma lookup engine also covers the
> > cases addressed by your patch:
>
> Your patch performs a few odd things like:
>
> + vma->vm_raend = 0;
> + vma->vm_pgoff += (start - vma->vm_start) >> PAGE_SHIFT;
> lock_vma_mappings(vma);
> spin_lock(&vma->vm_mm->page_table_lock);
> - vma->vm_pgoff += (start - vma->vm_start) >> PAGE_SHIFT;
>
> which I would argue are incorrect. Remember that page faults rely on
vm_raend is obviously correct.
For the vm_pgoff I need to think more about it (quite frankly I never
thought about expand_stack(), I only thought about the swapper locking
while doing the "odd" change), if it's a bug I will release a corrected
mmap-rb-5 in a few hours. Thanks for raising this issue.
> page_table_lock to protect against the case where the stack is grown and
> vm_start is modified. Aside from that, your patch is a sufficiently large
> change so as to be material for 2.5. Also, have you instrumented the rb
I'm not caring about 2.whatever here. However I will certainly try at
max to avoid any hack at this point even in 2.4 now that the rb works
apparently solid (AFIK as worse with a SMP race in vm_pgoff :).
> trees to see what kind of an effect it has on performance compared to the
> avl tree?
I posted some benchmark result a few minutes ago (the numbers says there
were no implementation bugs).
Andrea
--
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/
next prev parent reply other threads:[~2001-08-19 0:35 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-16 21:02 Ben LaHaise
2001-08-18 18:22 ` resend " Ben LaHaise
2001-08-18 23:27 ` Andrea Arcangeli
2001-08-19 0:10 ` Ben LaHaise
2001-08-19 0:35 ` Andrea Arcangeli [this message]
2001-08-19 0:50 ` Rik van Riel
2001-08-19 0:55 ` Andrea Arcangeli
2001-08-19 1:17 ` Andrea Arcangeli
2001-08-19 0:53 ` Andrea Arcangeli
2001-08-19 1:02 ` Andrea Arcangeli
2001-08-19 1:25 ` Andrea Arcangeli
2001-08-19 1:40 ` Andrea Arcangeli
2001-08-19 2:59 ` Andrea Arcangeli
2001-08-19 3:53 ` Andrea Arcangeli
2001-08-19 5:11 ` Andrea Arcangeli
2001-08-19 0:54 ` Rik van Riel
2001-08-19 1:00 ` Andrea Arcangeli
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=20010819023548.P1719@athlon.random \
--to=andrea@suse.de \
--cc=alan@redhat.com \
--cc=bcrl@redhat.com \
--cc=blizzard@redhat.com \
--cc=linux-mm@kvack.org \
--cc=torvalds@transmeta.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox