From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: moreau francis <francis_moreau2000@yahoo.fr>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Re : vm: weird behaviour when munmapping
Date: Fri, 17 Nov 2006 15:21:08 +0100 [thread overview]
Message-ID: <1163773268.5968.122.camel@twins> (raw)
In-Reply-To: <20061117141230.70698.qmail@web23105.mail.ird.yahoo.com>
On Fri, 2006-11-17 at 14:12 +0000, moreau francis wrote:
> Peter Zijlstra wrote:
> > No indeed. You seem confused with remaining and new.
> >
> > It has one VMA (A) it needs to split that into two pieces, it happens to
> > do it like (B,A') where A' is the old VMA object with new a start
> > address, and B is a new VMA object.
>
> Is there any rules to decide which VMA is the new one ?
The new object is the one allocated using:
new = kmem_cache_alloc(vm_area_cachep, SLAB_KERNEL);
> From what you wrote it seems that we call B the new object because
> it has a new end address...
No, because its newly allocated.
> From my point of view, I called B the old VMA simply because it's
> going to be destroyed...
Please read Mel Gorman's book on memory management to gain a better
understanding.
http://www.phptr.com/bookstore/product.asp?isbn=0131453483&rl=1
next prev parent reply other threads:[~2006-11-17 14:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-17 14:12 Re : vm: weird behaviour when munmapping moreau francis
2006-11-17 14:21 ` Peter Zijlstra [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-11-17 21:01 Francis Moreau
2006-11-18 13:55 ` Hugh Dickins
2006-11-20 11:30 ` Francis Moreau
2006-11-20 11:36 ` Hugh Dickins
2006-11-20 12:20 ` Hugh Dickins
2006-11-21 8:41 ` Francis Moreau
2006-11-17 13:43 moreau francis
2006-11-17 13:48 ` Peter Zijlstra
2006-11-17 12:50 moreau francis
2006-11-17 13:05 ` Peter Zijlstra
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=1163773268.5968.122.camel@twins \
--to=a.p.zijlstra@chello.nl \
--cc=francis_moreau2000@yahoo.fr \
--cc=linux-kernel@vger.kernel.org \
/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