From: Mark J Roberts <mjr@znex.org>
To: linux-kernel@vger.kernel.org
Subject: Arbitrary mlock() half-memory limit.
Date: Fri, 21 Mar 2003 03:51:39 -0600 [thread overview]
Message-ID: <20030321095139.GB1324@znex> (raw)
/* 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.
reply other threads:[~2003-03-21 9:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030321095139.GB1324@znex \
--to=mjr@znex.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®