linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: 'David Gibson' <david@gibson.dropbear.id.au>
To: Andrew Morton <akpm@osdl.org>
Cc: kenneth.w.chen@intel.com, wli@holomorphy.com, linux-mm@kvack.org
Subject: Re: [patch] hugetlb strict commit accounting - v3
Date: Fri, 10 Mar 2006 15:50:33 +1100	[thread overview]
Message-ID: <20060310045033.GH9776@localhost.localdomain> (raw)
In-Reply-To: <20060309204653.0f780ba1.akpm@osdl.org>

On Thu, Mar 09, 2006 at 08:46:53PM -0800, Andrew Morton wrote:
> "'David Gibson'" <david@gibson.dropbear.id.au> wrote:
> >
> > On Thu, Mar 09, 2006 at 07:14:58PM -0800, Chen, Kenneth W wrote:
> > > hugetlb strict commit accounting for shared mapping - v3
> > > 
> > > The a region reservation list is implementation as a linked list
> > > hanging off address_space i_data->private_list.  It turns out that
> > > clear_inode() was also looking at inode->i_data->private_list and
> > > if not empty, it think inode has dirty buffers and start clearing.
> > > Except it won't go very far before oops-ing.  That could happen if
> > > a reservation is made but no actual faulting. hugetlbfs_delete_inode
> > > and hugetlbfs_forget_inode doesn't call truncate_hugepages if there
> > > are no actual page in the page cache, leading to clear_inode to do
> > > bad thing.  Change that to always call truncate_hugepages even if
> > > there are no pages in page cache and to let the unreserve code to
> > > clear out the reservation linked list.
> > 
> > Hrm.. overloading the private_list in this manner sounds fragile.
> > Maybe we should move the list into the hugetlbfs specific inode data.
> 
> private_list and private_lock are available for use by the subsystem which
> owns this mapping's address_space_operations.  ie: hugetlbfs.

If that's so, why is clear_inode messing with it?

> It's been this way for several years but afaik this is the first time
> that's actually been taken advantage of.

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

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2006-03-10  4:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-10  3:14 Chen, Kenneth W
2006-03-10  4:37 ` 'David Gibson'
2006-03-10  4:46   ` Andrew Morton
2006-03-10  4:50     ` 'David Gibson' [this message]
2006-03-10  5:39       ` Andrew Morton
2006-03-10  5:48         ` Andrew Morton
2006-03-20 15:35 ` Adam Litke
2006-03-20 18:48 Chen, Kenneth W
2006-03-20 20:21 ` Adam Litke

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=20060310045033.GH9776@localhost.localdomain \
    --to=david@gibson.dropbear.id.au \
    --cc=akpm@osdl.org \
    --cc=kenneth.w.chen@intel.com \
    --cc=linux-mm@kvack.org \
    --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