From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Phy Prabab <phyprabab@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Non continuous VM address space
Date: Thu, 26 Apr 2007 16:46:35 -0700 [thread overview]
Message-ID: <463139DB.8070607@goop.org> (raw)
In-Reply-To: <2fe399760704261333g4dbf79a1p92be761d3680c9d7@mail.gmail.com>
Phy Prabab wrote:
> Sometimes the next memory
> allocation is several megs above where the previous mapping came from.
> Is this possible?
The kernel is free to place mmaped memory whereever it likes unless you
use MAP_FIXED and specify an address.
J
prev parent reply other threads:[~2007-04-26 23:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-26 20:33 Non continuous VM address space Phy Prabab
2007-04-26 23:46 ` Jeremy Fitzhardinge [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=463139DB.8070607@goop.org \
--to=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=phyprabab@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.