From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Christoph Hellwig <hch@infradead.org>
Cc: David Chinner <dgc@sgi.com>, lkml <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: [PATCH 1 of 2] block_page_mkwrite() Implementation V2
Date: Mon, 19 Mar 2007 21:11:31 +1100 [thread overview]
Message-ID: <45FE61D3.90105@yahoo.com.au> (raw)
In-Reply-To: <20070319092222.GA1720@infradead.org>
Christoph Hellwig wrote:
> On Mon, Mar 19, 2007 at 10:30:08AM +1100, David Chinner wrote:
>
>>Generic page_mkwrite functionality.
>>
>>Filesystems that make use of the VM ->page_mkwrite() callout will generally use
>>the same core code to implement it. There are several tricky truncate-related
>>issues that we need to deal with here as we cannot take the i_mutex as we
>>normally would for these paths. These issues are not documented anywhere yet
>>so block_page_mkwrite() seems like the best place to start.
>
>
> This will need some updates when ->fault replaces ->page_mkwrite.
>
> Nich, what's the plan for merging ->fault?
I've got the patches in -mm now. I hope they will get merged when the
the next window opens.
I didn't submit the ->page_mkwrite conversion yet, because I didn't
have any callers to look at. It is is slightly less trivial than for
nopage and nopfn, so having David's block_page_mkwrite is helpful.
--
SUSE Labs, Novell Inc.
Send instant messages to your online friends http://au.messenger.yahoo.com
WARNING: multiple messages have this Message-ID (diff)
From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Christoph Hellwig <hch@infradead.org>
Cc: David Chinner <dgc@sgi.com>, lkml <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: [PATCH 1 of 2] block_page_mkwrite() Implementation V2
Date: Mon, 19 Mar 2007 21:11:31 +1100 [thread overview]
Message-ID: <45FE61D3.90105@yahoo.com.au> (raw)
In-Reply-To: <20070319092222.GA1720@infradead.org>
Christoph Hellwig wrote:
> On Mon, Mar 19, 2007 at 10:30:08AM +1100, David Chinner wrote:
>
>>Generic page_mkwrite functionality.
>>
>>Filesystems that make use of the VM ->page_mkwrite() callout will generally use
>>the same core code to implement it. There are several tricky truncate-related
>>issues that we need to deal with here as we cannot take the i_mutex as we
>>normally would for these paths. These issues are not documented anywhere yet
>>so block_page_mkwrite() seems like the best place to start.
>
>
> This will need some updates when ->fault replaces ->page_mkwrite.
>
> Nich, what's the plan for merging ->fault?
I've got the patches in -mm now. I hope they will get merged when the
the next window opens.
I didn't submit the ->page_mkwrite conversion yet, because I didn't
have any callers to look at. It is is slightly less trivial than for
nopage and nopfn, so having David's block_page_mkwrite is helpful.
--
SUSE Labs, Novell Inc.
Send instant messages to your online friends http://au.messenger.yahoo.com
--
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:[~2007-03-19 10:11 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-18 23:30 [PATCH 1 of 2] block_page_mkwrite() Implementation V2 David Chinner
2007-03-18 23:30 ` David Chinner
2007-03-19 6:37 ` Nick Piggin
2007-03-19 6:37 ` Nick Piggin
2007-03-19 8:12 ` David Chinner
2007-03-19 8:12 ` David Chinner
2007-03-19 9:57 ` Nick Piggin
2007-03-19 9:57 ` Nick Piggin
2007-03-19 10:28 ` Nick Piggin
2007-03-19 10:28 ` Nick Piggin
2007-03-19 9:22 ` Christoph Hellwig
2007-03-19 9:22 ` Christoph Hellwig
2007-03-19 10:11 ` Nick Piggin [this message]
2007-03-19 10:11 ` Nick Piggin
2007-03-19 12:22 ` Christoph Hellwig
2007-03-19 12:22 ` Christoph Hellwig
2007-03-20 5:34 ` Nick Piggin
2007-03-20 5:34 ` Nick Piggin
2007-05-16 10:19 ` David Howells
2007-05-16 10:19 ` David Howells
2007-05-16 11:59 ` Nick Piggin
2007-05-16 11:59 ` Nick Piggin
2007-05-16 13:20 ` David Howells
2007-05-16 13:20 ` David Howells
2007-05-16 13:41 ` Nick Piggin
2007-05-16 13:41 ` Nick Piggin
2007-05-16 12:09 ` David Woodhouse
2007-05-16 12:09 ` David Woodhouse
2007-05-16 12:53 ` Chris Mason
2007-05-16 12:53 ` Chris Mason
2007-05-16 13:04 ` Nick Piggin
2007-05-16 13:04 ` Nick Piggin
2007-05-16 13:10 ` Chris Mason
2007-05-16 13:10 ` Chris Mason
2007-05-16 13:25 ` David Howells
2007-05-16 13:25 ` David Howells
2007-05-16 23:28 ` David Chinner
2007-05-16 23:28 ` David Chinner
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=45FE61D3.90105@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=dgc@sgi.com \
--cc=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.