From: "Phy Prabab" <phyprabab@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Non continuous VM address space
Date: Thu, 26 Apr 2007 13:33:41 -0700 [thread overview]
Message-ID: <2fe399760704261333g4dbf79a1p92be761d3680c9d7@mail.gmail.com> (raw)
Hello,
I have a question, I have a little application and sbrks and then
mmaps to get memory from the system. Originally, this program worked
fine because I had assumed that my applications address space would be
continuous, each subsequent memory request would "mapped" next to each
other, after all this is the address space for this process. However,
what I am finding is that the space is discontiguous, I am getting
back addresses not next to each other. Sometimes the next memory
allocation is several megs above where the previous mapping came from.
Is this possible? Or am I not accounting for something? Yes, I have
intentionally defined malloc, calloc, etc. so they can not be used
under the hood within my code.
BTW, seeing this on 2.6.9 and 2.4.(?) - these are both RH supplied kernels
TIA!
Phy
next reply other threads:[~2007-04-26 20:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-26 20:33 Phy Prabab [this message]
2007-04-26 23:46 ` Jeremy Fitzhardinge
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=2fe399760704261333g4dbf79a1p92be761d3680c9d7@mail.gmail.com \
--to=phyprabab@gmail.com \
--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
all inboxes | Powered by JetHome®