DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition;
        b=FdlCYr9NsY3GDlBYGVAjzx2z2Gnn0wdGnxs4MGqtisTyyjruassaNT44Pbmpif5fFzChxrFRDPIoYFOl+1xvOw4oRCwwQteX8XUThi4qLvuVZ/z43LsUoV5pZOV6tVYdkPSjjDNwKKeZ6v5MMpZPpjNAHUuavh8zL/Ny+/vl5c0=
Message-ID: <632b79000601181149o67f1c013jfecc5e32ee17fe7e@mail.gmail.com>
Date: Wed, 18 Jan 2006 13:49:21 -0600
From: Don Dupuis <dondster@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Can't mlock hugetlb in 2.6.15
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7BIT
Content-Disposition: inline
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 714
Lines: 16

I have an app that mlocks hugepages. The same app works just fine in 2.6.14.
This app has 128MB or more of shared memory that is using hugepages via
mmap. When I try this, I get the error "can't allocate memory".  Is this a
kernel bug or is this not supported anymore.  I want to guarantee that
this memory doesn't get swapped out to a swap device. I made the same
modifications to include/linux/resource.h that was in 2.6.14, which
set MLOCK_LIMIT to 2GB.

Thanks

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