Date: Fri, 21 Mar 2003 03:51:39 -0600
From: Mark J Roberts <mjr@znex.org>
To: linux-kernel@vger.kernel.org
Subject: Arbitrary mlock() half-memory limit.
Message-ID: <20030321095139.GB1324@znex>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 743
Lines: 17

	/* we may lock at most half of physical memory... */
	/* (this check is pretty bogus, but doesn't hurt) */
	if (locked > num_physpages/2)
		goto out;

I've been running fluidsynth (a synthesizer program) with 700-900MB
instrument sample files on a box with 1GB of memory. It tries to
lock the samples into memory and fails.

This isn't a problem for me, since I don't have swap configured and
the sample data is anonymous-backed, but it's a case in which the
arbitrary limit is clearly pernicious.
-
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/