Re: Can't mlock hugetlb in 2.6.15

[Nick Piggin]

Andrew Morton wrote:
> Don Dupuis <dondster@xxxxxxxxx> wrote:
>
> > 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.
>
>
> hugetlb areas are not pageable and it's very unlikely that they will become
> so in the forseeable future.  So you don't need to do this.
>
> That being said, we shouldn't have broken your application.

Yep, and it does not sound unreasonable to have mlock succeed on hugepage
areas (though I'm not reading any standardese). And you wouldn't expect
mlockall to fail if an app is using hugepages either.

I don't have an idea off the top of my head though. Don, an strace log of
the failing sequence of syscalls could be helpful.

--
SUSE Labs, Novell Inc.
Send instant messages to your online friends http://au.messenger.yahoo.com 
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/