linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: David Gibson <dwg@au1.ibm.com>
To: Adam Litke <agl@us.ibm.com>
Cc: sonnyrao@us.ibm.com, linuxppc-dev@ozlabs.org, anton@au1.ibm.com,
	libhugetlbfs-devel@lists.sourceforge.net, nacc@us.ibm.com
Subject: Re: [Libhugetlbfs-devel] 2.6.19: kernel BUG in hugepd_page at	arch/powerpc/mm/hugetlbpage.c:58!
Date: Wed, 24 Jan 2007 11:35:56 +1100	[thread overview]
Message-ID: <20070124003556.GA2218@localhost.localdomain> (raw)
In-Reply-To: <1169569203.14914.36.camel@localhost.localdomain>

On Tue, Jan 23, 2007 at 10:20:03AM -0600, Adam Litke wrote:
> On Tue, 2007-01-23 at 17:18 +1100, David Gibson wrote:
> > Second, there's the fact that we never demote hugepage segments back
> > to normal pages.  That was a deliberate decision to keep things
> > simple, incidentally, not simply an oversight.  I guess it would help
> > in this case and shouldn't be that hard.  It would mean a find_vma()
> > on each unmap to see if the region is now clear, but that's probably
> > not too bad.  Plus a bunch of on_each_cpu()ed slbies as when we open a
> > new hugepage segment.  Oh.. and making sure we get rid of any empty
> > hugepage directories, which might be a bit fiddly.
> 
> Could we also try lazy conversion of huge segments to normal ones?  When
> is_hugepage_only_range() detects overlapping hugepage ranges, it could
> attempt to "close" those ranges for huge pages first.  Then the heavy
> lifting only needs to happen when a small page mapping needs the space.

We could, but I think it's both easier and less operations to do the
check on unmap.  The lifting isn't that heavy.

-- 
David Gibson			| I'll have my music baroque, and my code
david AT gibson.dropbear.id.au	| minimalist, thank you.  NOT _the_ _other_
				| _way_ _around_!
http://www.ozlabs.org/~dgibson

      reply	other threads:[~2007-01-24  0:48 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-12 19:57 2.6.19: kernel BUG in hugepd_page at arch/powerpc/mm/hugetlbpage.c:58! Sonny Rao
2007-01-12 20:08 ` Adam Litke
2007-01-12 20:30   ` Sonny Rao
2007-01-12 21:11     ` Nishanth Aravamudan
2007-01-12 21:28       ` Sonny Rao
2007-01-12 20:42   ` Sonny Rao
2007-01-12 21:12     ` Nishanth Aravamudan
2007-01-12 22:43     ` [Libhugetlbfs-devel] " David Gibson
2007-01-23  5:10       ` Sonny Rao
2007-01-23  6:18         ` David Gibson
2007-01-23 16:20           ` Adam Litke
2007-01-24  0:35             ` David Gibson [this message]

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=20070124003556.GA2218@localhost.localdomain \
    --to=dwg@au1.ibm.com \
    --cc=agl@us.ibm.com \
    --cc=anton@au1.ibm.com \
    --cc=libhugetlbfs-devel@lists.sourceforge.net \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=nacc@us.ibm.com \
    --cc=sonnyrao@us.ibm.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).