Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Wed, 18 Sep 2002 15:35:11 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Wed, 18 Sep 2002 15:35:10 -0400 Received: from perninha.conectiva.com.br ([200.250.58.156]:62738 "HELO perninha.conectiva.com.br") by vger.kernel.org with SMTP id ; Wed, 18 Sep 2002 15:35:09 -0400 Date: Wed, 18 Sep 2002 16:39:48 -0300 (BRT) From: Rik van Riel X-X-Sender: riel@duckman.distro.conectiva To: Mark_H_Johnson@raytheon.com Cc: Andrew Morton , , , Subject: Re: [PATCH] recognize MAP_LOCKED in mmap() call In-Reply-To: Message-ID: X-spambait: aardvark@kernelnewbies.org X-spammeplease: aardvark@nl.linux.org MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 955 Lines: 29 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/