From owner-freebsd-hackers@FreeBSD.ORG  Tue Apr 10 17:08:58 2012
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
	by hub.freebsd.org (Postfix) with ESMTP id E95F91065672
	for <freebsd-hackers@freebsd.org>; Tue, 10 Apr 2012 17:08:58 +0000 (UTC)
	(envelope-from dieterbsd@engineer.com)
Received: from mailout-us.gmx.com (mailout-us.gmx.com [74.208.5.67])
	by mx1.freebsd.org (Postfix) with SMTP id B806F8FC17
	for <freebsd-hackers@freebsd.org>; Tue, 10 Apr 2012 17:08:58 +0000 (UTC)
Received: (qmail 31510 invoked by uid 0); 10 Apr 2012 17:08:57 -0000
Received: from 67.206.161.58 by rms-us006.v300.gmx.net with HTTP
Content-Type: text/plain; charset="utf-8"
Date: Tue, 10 Apr 2012 13:08:54 -0400
From: "Dieter BSD" <dieterbsd@engineer.com>
Message-ID: <20120410170855.155050@gmx.com>
MIME-Version: 1.0
To: freebsd-hackers@freebsd.org
X-Authenticated: #74169980
X-Flags: 0001
X-Mailer: GMX.com Web Mailer
x-registered: 0
Content-Transfer-Encoding: 8bit
X-GMX-UID: cAz2b/Vd3zOlNR3dAHAhnVd+IGRvbwBL
Subject: mlock/mlockall (was: Re: problems with mmap() and disk caching)
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Technical Discussions relating to FreeBSD
	<freebsd-hackers.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>, 
	<mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
	<mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Apr 2012 17:08:59 -0000

Andrey writes:
> Wired memory: kernel memory and yes, application may get wired memory
> through mlock()/mlockall(), but I haven't seen any real application
> which calls mlock().

Apps with real time considerations may need to lock memory to prevent
having to wait for page/swap.