From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Fix for for memory leak in IA32 mmap
Date: Tue, 05 Mar 2002 18:59:17 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590701905226@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590701905222@msgid-missing>
>>>>> On Tue, 5 Mar 2002 10:46:29 -0700, Don Dugger <n0ano@n0ano.com> said:
Don> David- Yep, it was a virtual memory leak. Intel came up with a
Don> Fortran program that was allocating and freeing lots of
Don> anonymous `mmap's. It was really nasty because it wasn't even
Don> the same request all the time, it had something like 3
Don> different odd size requests that it was `mmap'ing and
Don> `munmap'ing, all in a loop and eventually it ran out of VM.
OK, thanks for the background.
Don> I like the idea of keeping a bitmap. I still have to keep a
Don> list, it'll actually be a bigger list since I'll have to keep
Don> track of fixed requests also, but that should handle ALL cases
Don> (even the case where a program makes an odd sized non-fixed
Don> `mmap' followed by a fixed `mmap' into the middle of the last
Don> page). Give me a few days and I'll see if I can't come up with
Don> something.
Yes, I agree: the list is still needed and an entry needs to be
created whenever an ia64 page is partially mapped.
Thanks,
--david
next prev parent reply other threads:[~2002-03-05 18:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-05 15:13 [Linux-ia64] Fix for for memory leak in IA32 mmap Don Dugger
2002-03-05 17:34 ` David Mosberger
2002-03-05 17:46 ` Don Dugger
2002-03-05 18:59 ` David Mosberger [this message]
2002-03-05 19:44 ` Luck, Tony
2002-03-05 20:06 ` n0ano
2002-03-05 20:09 ` David Mosberger
2002-03-05 21:49 ` Luck, Tony
2002-03-05 22:18 ` n0ano
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=marc-linux-ia64-105590701905226@msgid-missing \
--to=davidm@napali.hpl.hp.com \
--cc=linux-ia64@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