linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nick Piggin <npiggin@suse.de>
To: Christoph Hellwig <hch@infradead.org>
Cc: Linux Memory Management List <linux-mm@kvack.org>,
	linux-fsdevel@vger.kernel.org
Subject: Re: [patch 1/2] mm: page_mkwrite change prototype to match fault
Date: Wed, 4 Mar 2009 11:21:07 +0100	[thread overview]
Message-ID: <20090304102107.GE27043@wotan.suse.de> (raw)
In-Reply-To: <20090303155835.GA28851@infradead.org>

On Tue, Mar 03, 2009 at 10:58:35AM -0500, Christoph Hellwig wrote:
> On Tue, Mar 03, 2009 at 11:38:38AM +0100, Nick Piggin wrote:
> > 
> > Change the page_mkwrite prototype to take a struct vm_fault, and return
> > VM_FAULT_xxx flags. Same as ->fault handler. Should be no change in
> > behaviour.
> 
> How about just merging it into ->fault?
> 
> > This is required for a subsequent fix. And will also make it easier to
> > merge page_mkwrite() with fault() in future.
> 
> Ah, I should read until the end :)  Any reason not to do the merge just
> yet?

Getting there... after my proposed locking change as well it should
be even another step closer.

The only thing is that we probably need to keep the page_mkwrite callback
in the fs layer, but just move it out of the VM. Because it is hard to
make a generic fault function that does the right page_mkwrite thing
for all filesystems.

But at least pushing it down that step will give better efficiency and
be simpler in the VM. (full page fault today has to lock and unlock the
page 3 times with page_mkwrite, wheras it should go to 2 after my locking
change, and then 1 when page_mkwrite gets merged into fault).

It's coming... just a bit slowly.

  reply	other threads:[~2009-03-04 10:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-03 10:38 [patch 1/2] mm: page_mkwrite change prototype to match fault Nick Piggin
2009-03-03 10:41 ` [rfc][patch 2/2] buffer, btrfs: fix page_mkwrite error cases Nick Piggin
2009-03-03 14:26   ` Chris Mason
2009-03-03 14:41     ` Nick Piggin
2009-03-03 14:47       ` Chris Mason
2009-03-03 12:39 ` [patch 1/2] mm: page_mkwrite change prototype to match fault steve
2009-03-03 15:58 ` Christoph Hellwig
2009-03-04 10:21   ` Nick Piggin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-03-11  3:53 Nick Piggin

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=20090304102107.GE27043@wotan.suse.de \
    --to=npiggin@suse.de \
    --cc=hch@infradead.org \
    --cc=linux-fsdevel@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 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).