From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: vamsi krishna <vamsi.krishnak@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Increasing virtual address space of a process, by treating virtual address's as offsets in secondary memory.
Date: Mon, 18 Jul 2005 12:45:52 +0100 [thread overview]
Message-ID: <1121687153.12438.5.camel@localhost.localdomain> (raw)
In-Reply-To: <3faf056805071721422594dd20@mail.gmail.com>
On Llu, 2005-07-18 at 10:12 +0530, vamsi krishna wrote:
> I was searching a lot about work on this, and found your reply where
> you say that we can increase the virtual address space by mmaping and
> munmaping programatically ourself.
Its something a few giant applications do with data sets and the trick
of using shared memory segments works on most Linux or Unixlike systems.
It's almost a historical note now. With 64bit processors its no longer
worth the pain
prev parent reply other threads:[~2005-07-18 11:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-18 4:42 vamsi krishna
2005-07-18 11:45 ` Alan Cox [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=1121687153.12438.5.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=vamsi.krishnak@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 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®