lkml.org 
[lkml]   [2005]   [Jun]   [29]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: **** How to lock memory pages?
>>>>> "Richard" == Richard B Johnson <linux-os@analogic.com> writes:

Richard> On Wed, 29 Jun 2005, Sreeni wrote:

>> Is there a way to lock a particular portion of the memory pages during
>> kernel bootup? I want to re-use these pages when I load my
>> application. I *don't* wanna use the idea of reserving some physical
>> memory and using ioremap. I want something that kernel should be able
>> to manage this memory but I don't want any other application to use
>> this memory.

Richard> Wrong kind of kernel for this kind of use. The kernel
Richard> dynamically allocates/deallocates/pages of memory that it
Richard> knows about. The only way to do what you want, with a kernel
Richard> designed for multi-tasking multi-user applications use, is to
Richard> reserve memory during boot.

Sreeni, you might want to look at the mlockall() interface, but it's
also hard to know what's right to do here if you don't explain what
you are trying to do. For example, why do you *care* which memory
address(es) your application gets?

John
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-06-29 22:07    [W:0.054 / U:0.408 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site