From: David Luyer <david_luyer@pacific.net.au>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [LONGish] Brief analysis of VMAs (was: /proc/<n>/maps getting
Date: 07 Aug 2001 12:26:40 +1000 [thread overview]
Message-ID: <997151200.10551.15.camel@typhaon> (raw)
In-Reply-To: <E15Tk4u-0000wy-00@the-village.bc.nu>
In-Reply-To: <E15Tk4u-0000wy-00@the-village.bc.nu>
On 06 Aug 2001 14:05:52 +0100, Alan Cox wrote:
> > Yes, that's what's happening above. And it's what's causing the
> > splits in the vmas. So basically evolution-mail is doing exactly what
> > your test program was doing, and causing exactly the same thing.
> >
> > Seems strange that glibc would do this unless there was some performance
> > reason on past kernels to do it?
>
> Are you sure thats not evolution being built with a debugging malloc of
> some kind ?
Yes, as per cw's e-mail it's just how malloc() works in some cases on
glibc. Allocate 2 * sz (where sz is a relatively large amount compared
to the amount being malloc()'d), free up the 'sz' which is not aligned
to a multiple of 'sz', and the gradually mprotect(PROT_READ|PROT_WRITE)
the memory it's allocated initially with PROT_NONE and MAP_NORESERVE.
And mprotect() responds by splitting up the vmas and never merging them
back together.
--
David Luyer Phone: +61 3 9674 7525
Engineering Projects Manager P A C I F I C Fax: +61 3 9699 8693
Pacific Internet (Australia) I N T E R N E T Mobile: +61 4 1111 2983
http://www.pacific.net.au/ NASDAQ: PCNTF
prev parent reply other threads:[~2001-08-07 2:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-06 10:18 [LONGish] Brief analysis of VMAs (was: /proc/<n>/maps getting _VERY_ long David Luyer
2001-08-06 13:05 ` [LONGish] Brief analysis of VMAs (was: /proc/<n>/maps getting Alan Cox
2001-08-06 13:11 ` Chris Wedgwood
2001-08-07 2:26 ` David Luyer [this message]
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=997151200.10551.15.camel@typhaon \
--to=david_luyer@pacific.net.au \
--cc=alan@lxorguk.ukuu.org.uk \
--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