From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Andrew Morton <akpm@osdl.org>
Cc: Don Dupuis <dondster@gmail.com>,
linux-kernel@vger.kernel.org, Hugh Dickins <hugh@veritas.com>
Subject: Re: Can't mlock hugetlb in 2.6.15
Date: Sun, 22 Jan 2006 01:12:55 +1100 [thread overview]
Message-ID: <43D24167.1010007@yahoo.com.au> (raw)
In-Reply-To: <20060120235240.39d34279.akpm@osdl.org>
Andrew Morton wrote:
> Don Dupuis <dondster@gmail.com> 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
next prev parent reply other threads:[~2006-01-21 14:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-18 19:49 Can't mlock hugetlb in 2.6.15 Don Dupuis
2006-01-21 7:52 ` Andrew Morton
2006-01-21 14:12 ` Nick Piggin [this message]
2006-01-23 2:32 ` Don Dupuis
2006-01-23 19:51 ` Hugh Dickins
2006-01-23 20:53 ` Don Dupuis
2006-01-23 21:34 ` Adam Litke
2006-01-23 23:52 ` William Lee Irwin III
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=43D24167.1010007@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=akpm@osdl.org \
--cc=dondster@gmail.com \
--cc=hugh@veritas.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.