From: Hugh Dickins <hugh@veritas.com>
To: Anton Altaparmakov <aia21@cam.ac.uk>
Cc: David Howells <dhowells@redhat.com>,
Christoph Hellwig <hch@infradead.org>,
Andrew Morton <akpm@osdl.org>, Carsten Otte <cotte@de.ibm.com>,
linux-kernel@vger.kernel.org
Subject: Re: what happened to page_mkwrite? - was: Re: page_mkwrite seems broken
Date: Mon, 24 Oct 2005 17:01:53 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.61.0510241648170.4338@goblin.wat.veritas.com> (raw)
In-Reply-To: <1130168619.19518.43.camel@imp.csi.cam.ac.uk>
On Mon, 24 Oct 2005, Anton Altaparmakov wrote:
>
> I don't really mind either way. I am stuck with ntfs at the moment at
> the point where I am either going to use my own ->nopage handler to
> allocate on-disk clusters or have a ->page_mkwrite handler do it. The
> former is not nice as it means we allocate space even when only reading
> whilst the later is very nice as it only triggers when someone actually
> does an mmapped write.
A complication to beware of there (and I may be misunderstanding, but
the point is worth making). If you have already mmaped readonly zero
pages into some mms, you'll need to update those mms with the new
shared writable pages once they are allocated. That put me off using
page_mkwrite in tmpfs, but Carsten has solved the problem (though
not going so far as to use page_mkwrite) with his xip_file_nopage
in mm/filemap_xip.c - has to go down the vma_prio_tree like rmap.
(That code is a little different in -mm, partly because of my page
table locking changes, partly because of Nick's ZERO_PAGE changes.)
Hmm, strictly speaking, it should be substituting the new page
when VM_LOCKED: whether that's worth the effort of implementing....
Hugh
next prev parent reply other threads:[~2005-10-24 16:02 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-09 14:28 Hugh Dickins
2005-10-24 15:16 ` what happened to page_mkwrite? - was: " Anton Altaparmakov
2005-10-24 15:36 ` Hugh Dickins
2005-10-24 15:49 ` Anton Altaparmakov
2005-10-24 15:26 ` David Howells
2005-10-24 15:43 ` Anton Altaparmakov
2005-10-24 16:01 ` Hugh Dickins [this message]
2005-10-24 19:38 ` Anton Altaparmakov
2005-10-24 20:31 ` Hugh Dickins
2005-10-24 21:18 ` Anton Altaparmakov
2005-10-24 16:23 ` [PATCH] Add notification of page becoming writable to VMA ops David Howells
2005-10-24 19:11 ` Hugh Dickins
2005-10-25 7:59 ` Anton Altaparmakov
2005-10-25 8:26 ` Hugh Dickins
2005-10-25 8:49 ` Anton Altaparmakov
2005-10-25 9:49 ` David Howells
2005-10-25 9:55 ` David Howells
2005-10-25 10:12 ` David Howells
2005-10-25 13:18 ` [PATCH] Add notification of page becoming writable to VMA ops [try #2] David Howells
2005-11-30 13:58 ` [PATCH] Add notification of page becoming writable to VMA ops [try #3] David Howells
2005-11-30 14:40 ` Miklos Szeredi
2005-11-30 14:50 ` David Howells
2005-11-30 15:20 ` [PATCH] Add notification of page becoming writable to VMA ops [try #4] David Howells
2006-01-11 12:19 ` [PATCH] Add notification of page becoming writable to VMA ops [try #5] David Howells
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.61.0510241648170.4338@goblin.wat.veritas.com \
--to=hugh@veritas.com \
--cc=aia21@cam.ac.uk \
--cc=akpm@osdl.org \
--cc=cotte@de.ibm.com \
--cc=dhowells@redhat.com \
--cc=hch@infradead.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®