linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nick Piggin <npiggin@suse.de>
To: Andrew Morton <akpm@linux-foundation.org>,
	linux-fsdevel@vger.kernel.org, mhalcrow@us.ibm.com,
	phillip@hellewell.homeip.net, sfrench@samba.org,
	dhowells@redhat.com
Subject: [rfc][patches] remove ->prepare_write
Date: Mon, 12 Nov 2007 08:12:45 +0100	[thread overview]
Message-ID: <20071112071245.GB22953@wotan.suse.de> (raw)

Hi,

These are a set of patches to convert the last few filesystems to use
the new deadlock-free write aops, and remove the core code to handle the
legacy write path.

I don't really have setups to sufficiently test these filesystems. So I
would really appreciate if filesystem maintainers can pick these patches
up, bear with my bugs, and send them upstream when they're ready.

The benefit to you is that you get to use the fast and well tested code 
paths! Actually, it is interesting: several of the conversions I've done
(including these) take a relatively naive aproach of simply prefilling
the whole page if it isn't uptodate. It might be the case that some
filesystems actually prefer to do something similar to the legacy
double-copy path which they're being converted away from! (then again,
it would be probably even more ideal to have simple sub-page state
tracking structures).

There is still quite a lot of work left to be done. Several filesystems
still use prepare_write() helpers, and when they're fixed up, all the
old helpers themselves have to be removed. But this step is probably
most important to getting rid of complex code.




             reply	other threads:[~2007-11-12  7:12 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-12  7:12 Nick Piggin [this message]
2007-11-12  7:13 ` [rfc][patch 1/5] ecryptfs new aops Nick Piggin
2007-11-12  7:14 ` [rfc][patch 2/5] cifs: " Nick Piggin
2007-11-12  7:14 ` [rfc][patch 3/5] afs: " Nick Piggin
2007-11-12  7:20 ` [rfc][patch 4/5] rd: rewrite rd Nick Piggin
2007-11-12  7:23 ` [rfc][patch 5/5] remove prepare_write Nick Piggin
2007-11-12 15:29 ` [rfc][patch 3/5] afs: new aops David Howells
2007-11-13  0:15   ` Nick Piggin
2007-11-13  0:30   ` David Howells
2007-11-13  0:44     ` Nick Piggin
2007-11-13 10:56     ` David Howells
2007-11-14  4:24       ` Nick Piggin
2007-11-14 12:18       ` David Howells
2007-11-14 15:18         ` Nick Piggin
2007-11-14 15:57         ` David Howells
2007-11-14 21:32           ` Nick Piggin
2007-11-15 12:15           ` David Howells
2007-11-15 21:37             ` 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=20071112071245.GB22953@wotan.suse.de \
    --to=npiggin@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=dhowells@redhat.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=mhalcrow@us.ibm.com \
    --cc=phillip@hellewell.homeip.net \
    --cc=sfrench@samba.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).