Re: [PATCH] recognize MAP_LOCKED in mmap() call

From: Rik van Riel (riel@conectiva.com.br)
Date: Wed Sep 18 2002 - 14:39:48 EST

Next message: Kari Hameenaho: "2.5.36 X freezes and input problems"
Previous message: Lev Makhlis: "Re: [RFC][PATCH] sard changes for 2.5.34"
In reply to: Mark_H_Johnson@raytheon.com: "Re: [PATCH] recognize MAP_LOCKED in mmap() call"
Next in thread: Andrew Morton: "Re: [PATCH] recognize MAP_LOCKED in mmap() call"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On Wed, 18 Sep 2002 Mark_H_Johnson@raytheon.com wrote:
> Andrew Morton wrote:
> >(SuS really only anticipates that mmap needs to look at prior mlocks
> >in force against the address range. It also says
> >
> > Process memory locking does apply to shared memory regions,
> >
> >and we don't do that either. I think we should; can't see why SuS
> >requires this.)
>
> Let me make sure I read what you said correctly. Does this mean that
> Linux 2.4 (or 2.5) kernels do not lock shared memory regions if a
> process uses mlockall?

But it does. Linux won't evict memory that's MLOCKed...

cheers,

Rik

-- Spamtrap of the month: september@surriel.com

http://www.surriel.com/ http://distro.conectiva.com/

- 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/

Next message: Kari Hameenaho: "2.5.36 X freezes and input problems"
Previous message: Lev Makhlis: "Re: [RFC][PATCH] sard changes for 2.5.34"
In reply to: Mark_H_Johnson@raytheon.com: "Re: [PATCH] recognize MAP_LOCKED in mmap() call"
Next in thread: Andrew Morton: "Re: [PATCH] recognize MAP_LOCKED in mmap() call"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Mon Sep 23 2002 - 22:00:24 EST