From: Bryan Donlan <bdonlan@gmail.com>
To: Siddhartha Chhabra <siddhartha.chhabra@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Controlling memory allocation
Date: Sat, 12 Sep 2009 13:28:03 -0400 [thread overview]
Message-ID: <3e8340490909121028g67b63fadh8d37a975da34c18f@mail.gmail.com> (raw)
In-Reply-To: <49f90a800909112201v7853be05mbd678dcb5fd20c5a@mail.gmail.com>
On Sat, Sep 12, 2009 at 1:01 AM, Siddhartha Chhabra
<siddhartha.chhabra@gmail.com> wrote:
> I hope I am making some sense, so in essence my question can be re-framed
> as, can the kernel "virtualize" memory for a particular process so only a
> particular region of the memory is available for that particular process and
> all other activities like page allocation and replacement take place for
> this process only within this region and rest of the system functions
> normally with the entire memory available for use
>
> Thanks once again for your reply and I really appreciate all the help
I'm not an expert on the Linux memory manager, but I don't think what
you're asking has been implemented in the kernel - although it might
be useful for your particular research, it's not really useful in the
real world, so nobody's had a need to implement it. Of course, feel
free to do so yourself :)
PS - I received two copies of the message with different message IDs.
When replying to this message, just use reply to all from gmail, don't
copy and paste it into nabble as well. The CC will make sure it gets
to lkml.
prev parent reply other threads:[~2009-09-12 17:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-12 2:23 sidc7
2009-09-12 3:37 ` Bryan Donlan
2009-09-12 5:02 ` sidc7
[not found] ` <49f90a800909112201v7853be05mbd678dcb5fd20c5a@mail.gmail.com>
2009-09-12 17:28 ` Bryan Donlan [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=3e8340490909121028g67b63fadh8d37a975da34c18f@mail.gmail.com \
--to=bdonlan@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=siddhartha.chhabra@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®