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:53:14 +0200 [thread overview]
Message-ID: <20010819025314.R1719@athlon.random> (raw)
In-Reply-To: <20010819023548.P1719@athlon.random>; from andrea@suse.de on Sun, Aug 19, 2001 at 02:35:48AM +0200
On Sun, Aug 19, 2001 at 02:35:48AM +0200, Andrea Arcangeli wrote:
> 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.
I don't think it's a bug so I don't feel the need to change it. The
expand_stack can only run with the semaphore acquired at worse in read
mode so it cannot race.
However now that you make me to think about this vm_pgoff field I'm
afraid I forgot to update it in the forward merging cases (in the new
code), luckily there are only a few forward merging cases that we have
to do (the backmerging are much more frequent) so it will be trivial to
fix it (and since I only merge anon mappings the bug seems only
theorical and this is probably why I couldn't notice it while doing the
regression testing [but I certainly agree to fix it even if it's
theorical]).
If I'm missing something let me know of course, thanks,
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:53 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-16 21:02 [PATCH] final merging patch -- significant mozilla speedup 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
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 [this message]
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 3:53 ` Andrea Arcangeli
2001-08-19 5:11 ` 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=20010819025314.R1719@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 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.