From: Hugh Dickins <hugh@veritas.com>
To: 'David Gibson' <david@gibson.dropbear.id.au>
Cc: "Chen, Kenneth W" <kenneth.w.chen@intel.com>,
g@ozlabs.org, Andrew Morton <akpm@osdl.org>,
'Christoph Lameter' <christoph@schroedinger.engr.sgi.com>,
bill.irwin@oracle.com, Adam Litke <agl@us.ibm.com>,
linux-mm@kvack.org
Subject: Re: [RFC] reduce hugetlb_instantiation_mutex usage
Date: Tue, 31 Oct 2006 12:48:13 +0000 (GMT) [thread overview]
Message-ID: <Pine.LNX.4.64.0610311239460.6523@blonde.wat.veritas.com> (raw)
In-Reply-To: <20061031110540.GA14172@localhost.localdomain>
On Tue, 31 Oct 2006, 'David Gibson' wrote:
> On Mon, Oct 30, 2006 at 09:15:20PM -0800, Chen, Kenneth W wrote:
> >
> > Instead, I'm asking how private mapping protect race between file truncation
> > and fault? For shared mapping, it is clear to me that we are using lock_page
> > to protect file truncate with fault. But I don't see that protection with
> > private mapping in current upstream kernel.
>
> Oh, ok. I can't see how it matters in the PRIVATE case, given that
> truncate() won't, and shouldn't, truncate privately mapped pages.
Bzzt, it does and should (unless we decide to make hugetlbfs pages diverge
from the standard for ordinary pages in this respect - could do, but that
would require thought of its own). If you've been thinking otherwise,
that may explain why some of the accounting goes wrong.
Hugh
--
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>
next prev parent reply other threads:[~2006-10-31 12:48 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-26 22:17 Chen, Kenneth W
2006-10-26 22:44 ` Andrew Morton
2006-10-26 23:31 ` 'David Gibson'
2006-10-27 0:04 ` Andrew Morton
2006-10-27 3:11 ` 'David Gibson'
2006-10-27 3:35 ` Andrew Morton
2006-10-27 4:06 ` 'David Gibson'
2006-10-31 2:54 ` Chen, Kenneth W
2006-10-31 3:17 ` 'David Gibson'
2006-10-31 5:15 ` Chen, Kenneth W
2006-10-31 11:05 ` 'David Gibson'
2006-10-31 12:48 ` Hugh Dickins [this message]
2006-11-01 6:18 ` Nick Piggin
2006-11-01 10:17 ` Chen, Kenneth W
2006-11-02 3:06 ` Nick Piggin
2006-11-02 2:29 ` 'David Gibson'
2006-10-27 1:47 ` 'David Gibson'
2006-10-30 20:55 ` Adam Litke
2006-10-26 23:47 ` 'David Gibson'
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=Pine.LNX.4.64.0610311239460.6523@blonde.wat.veritas.com \
--to=hugh@veritas.com \
--cc=agl@us.ibm.com \
--cc=akpm@osdl.org \
--cc=bill.irwin@oracle.com \
--cc=christoph@schroedinger.engr.sgi.com \
--cc=david@gibson.dropbear.id.au \
--cc=g@ozlabs.org \
--cc=kenneth.w.chen@intel.com \
--cc=linux-mm@kvack.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox