linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Don Dupuis <dondster@gmail.com>
To: Hugh Dickins <hugh@veritas.com>
Cc: Nick Piggin <nickpiggin@yahoo.com.au>,
	Andrew Morton <akpm@osdl.org>, Adam Litke <agl@us.ibm.com>,
	William Irwin <wli@holomorphy.com>,
	linux-kernel@vger.kernel.org
Subject: Re: Can't mlock hugetlb in 2.6.15
Date: Mon, 23 Jan 2006 14:53:28 -0600	[thread overview]
Message-ID: <632b79000601231253q397ebc31odd5bb8ddc9f5bf3c@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0601231917210.5915@goblin.wat.veritas.com>

On 1/23/06, Hugh Dickins <hugh@veritas.com> wrote:
> On Sun, 22 Jan 2006, Don Dupuis wrote:
> > On 1/21/06, Nick Piggin <nickpiggin@yahoo.com.au> wrote:
> > > 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.
> > > > That being said, we shouldn't have broken your application.
> > > Don, an strace log of the failing sequence of syscalls could be helpful.
> >
> > sducstart:
> > open("/pivot3/mem/sduc", O_RDWR|O_CREAT, 0666) = 3
> > mmap2(NULL, 1761607680, PROT_READ|PROT_WRITE, MAP_SHARED|MAP_LOCKED,
> > 3, 0) = 0x4e000000
> >
> > This is the strace output of sductest that is a test program to access
> > the shared memory that was setup by sducstart:
> > open("/pivot3/mem/sduc", O_RDWR)        = 3
> > mmap2(NULL, 4194304, PROT_READ|PROT_WRITE, MAP_SHARED|MAP_LOCKED, 3,
> > 0) = -1 ENOMEM (Cannot allocate memory)
>
> Thanks a lot for the strace, that indeed helped to track it down.
>
> This has nothing to do with mlock or MAP_LOCKED - which by the way do
> make more sense in 2.6.15, since they provide a way of prefaulting the
> hugepage area like in earlier releases (now hugepages are being faulted
> in on demand, though never paged out, as Andrew said).
>
> Please try the patch below, and let us know if it works for you - thanks.
> Looks like we'll need this in 2.6.16-rc-git and 2.6.15-stable.
>
>
> 2.6.15's hugepage faulting introduced huge_pages_needed accounting into
> hugetlbfs: to count how many pages are already in cache, for spot check
> on how far a new mapping may be allowed to extend the file.  But it's
> muddled: each hugepage found covers HPAGE_SIZE, not PAGE_SIZE.  Once
> pages were already in cache, it would overshoot, wrap its hugepages
> count backwards, and so fail a harmless repeat mapping with -ENOMEM.
> Fixes the problem found by Don Dupuis.
>
> Signed-off-by: Hugh Dickins <hugh@veritas.com>
> ---
>
>  fs/hugetlbfs/inode.c |    4 ++--
>  1 files changed, 2 insertions(+), 2 deletions(-)
>
> --- 2.6.15/fs/hugetlbfs/inode.c 2006-01-03 03:21:10.000000000 +0000
> +++ linux/fs/hugetlbfs/inode.c  2006-01-23 18:39:47.000000000 +0000
> @@ -71,8 +71,8 @@ huge_pages_needed(struct address_space *
>         unsigned long start = vma->vm_start;
>         unsigned long end = vma->vm_end;
>         unsigned long hugepages = (end - start) >> HPAGE_SHIFT;
> -       pgoff_t next = vma->vm_pgoff;
> -       pgoff_t endpg = next + ((end - start) >> PAGE_SHIFT);
> +       pgoff_t next = vma->vm_pgoff >> (HPAGE_SHIFT - PAGE_SHIFT);
> +       pgoff_t endpg = next + hugepages;
>
>         pagevec_init(&pvec, 0);
>         while (next < endpg) {
>

This patch fixed my problem.

Thanks very much

Don

  reply	other threads:[~2006-01-23 20:53 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
2006-01-23  2:32     ` Don Dupuis
2006-01-23 19:51       ` Hugh Dickins
2006-01-23 20:53         ` Don Dupuis [this message]
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=632b79000601231253q397ebc31odd5bb8ddc9f5bf3c@mail.gmail.com \
    --to=dondster@gmail.com \
    --cc=agl@us.ibm.com \
    --cc=akpm@osdl.org \
    --cc=hugh@veritas.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nickpiggin@yahoo.com.au \
    --cc=wli@holomorphy.com \
    /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;
as well as URLs for NNTP newsgroup(s).