From: "Olivier, JeffreyX" <jeffreyx.olivier@intel.com>
To: linux-ia64@vger.kernel.org
Subject: RE: [Linux-ia64] mmap and malloc questions on IA-64 linux
Date: Fri, 02 Aug 2002 15:25:50 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590701905884@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590701905877@msgid-missing>
> - /proc/PID/maps (where PID is the process ids of the "interesting"
> tasks)
Thanks for the response.
/proc/PID/maps appears to be showing any entry for every single page in the
mapped files. Is this normal? Shouldn't there just be one map for the
whole file? At any rate, the mappings appear to be in the address range
described in the next paragraph.
Also, I started printing the addresses returned by malloc. I map the files
starting at 0x6000000300000000. The addresses for malloc are not getting
anywhere close to that limit. However, something very peculiar happens.
Just before the failed malloc, the last 3 or 4 successful mallocs return
addresses in the 0x2000000000000000 range which is region 1 and should(?) be
reserved for shared memory (according to the figure on page 149 or your ia64
kernel book). Any idea why this would happen. I don't explicitly allocate
memory as shared. At the point where this happens, the current brk is at
0x6000000000898000. That is almost 12 GB from the first mmap.
Here is the output of free just before it runs out of memory
total used free shared buffers cached
Mem: 952576 948448 4128 0 656 836416
-/+ buffers/cache: 111376 841200
Swap: 1542176 650992 891184
To explain the large number of cached pages, /proc/sys/vm/pagecache is
currently set to
2 15 75
Thanks,
Jeff
next prev parent reply other threads:[~2002-08-02 15:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-01 16:47 [Linux-ia64] mmap and malloc questions on IA-64 linux Olivier, JeffreyX
2002-08-01 18:09 ` David Mosberger
2002-08-02 15:25 ` Olivier, JeffreyX [this message]
2002-08-02 21:08 ` David Mosberger
2002-08-05 15:40 ` Olivier, JeffreyX
2002-08-05 20:31 ` David Mosberger
2002-08-05 21:01 ` Matthew Wilcox
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-105590701905884@msgid-missing \
--to=jeffreyx.olivier@intel.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