lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Message-ID: <3e8340490909121028g67b63fadh8d37a975da34c18f@mail.gmail.com>
Date:	Sat, 12 Sep 2009 13:28:03 -0400
From:	Bryan Donlan <bdonlan@...il.com>
To:	Siddhartha Chhabra <siddhartha.chhabra@...il.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Controlling memory allocation

On Sat, Sep 12, 2009 at 1:01 AM, Siddhartha Chhabra
<siddhartha.chhabra@...il.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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ