Messages in this thread | | | Date | Tue, 22 Jul 2003 15:12:59 +0200 | From | Gábor Lénárt <> | Subject | Re: vmalloc - kmalloc and page locks |
| |
Errrrr ... Sorry, I did not read your mail carefully ;-( I meant in case of a user process you can use mlock() and such :) AFAIK the kernel itself is not pagable ...
On Tue, Jul 22, 2003 at 03:07:18PM +0200, Gábor Lénárt wrote: > Please read something about the mlock() and/or mlockall() functions. > The prototype can be found in [/usr/include/]sys/mman.h > You can read there: > > /* Guarantee all whole pages mapped by the range [ADDR,ADDR+LEN) to > be memory resident. */ > extern int mlock (__const void *__addr, size_t __len) __THROW; > [...] > /* Cause all currently mapped pages of the process to be memory resident > until unlocked by a call to the `munlockall', until the process exits, > or until the process calls `execve'. */ > extern int mlockall (int __flags) __THROW; > > On Tue, Jul 22, 2003 at 06:00:14AM -0700, Deas, Jim wrote: > > How can I look at what memory are being paged out of memory in the kernel > > or how to lock kmalloc and vmalloc pages so they do not get put to swap? > [...] > > - Gábor (larta'H) > - > 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/
-- - Gábor (larta'H) - 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/
| |