All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: viro@zeniv.linux.org.uk, npiggin@suse.de
Cc: jack@suse.cz, linux-fsdevel@vger.kernel.org
Subject: [PATCH 0/6] first step toward the new truncate sequence
Date: Sun, 30 May 2010 22:49:32 +0200	[thread overview]
Message-ID: <20100530204932.GA21002@lst.de> (raw)

This series is something that I see as the first major step towards
a broad switch to the new truncate sequence.  The patches get rid
of the _newtrunc variant of blockdev_direct_IO & friends and
*_write_begin, and clean up some bits in that area that make the
switch easier.  After this we have all vmtruncate instances except
for inode_setattr in filesystem code.  A second series to deal
with ->setattr will follow and after that we can easily switch
over one filesystem after another.

I think this is still 2.6.34 material as it will make the fs
switches a lot easier and avoid introducing the _newtrunc variants
for one kernel release.

             reply	other threads:[~2010-05-30 20:49 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-30 20:49 Christoph Hellwig [this message]
2010-05-30 20:49 ` [PATCH 1/6] sort out blockdev_direct_IO variants Christoph Hellwig
2010-06-01 23:00   ` Jan Kara
2010-06-01 23:12     ` Christoph Hellwig
2010-06-01 23:16       ` Jan Kara
2010-05-30 20:49 ` [PATCH 2/6] get rid of nobh_write_begin_newtrunc Christoph Hellwig
2010-05-30 20:50 ` [PATCH 3/6] get rid of cont_write_begin_newtrunc Christoph Hellwig
2010-05-30 20:50 ` [PATCH 4/6] clean up write_begin usage for directories in pagecache Christoph Hellwig
2010-05-30 20:50 ` [PATCH 5/6] introduce __block_write_begin Christoph Hellwig
2010-05-31  8:10   ` Christoph Hellwig
2010-06-01 23:39   ` Jan Kara
2010-06-02  7:25     ` Christoph Hellwig
2010-06-02  9:47       ` Jan Kara
2010-05-30 20:50 ` [PATCH 6/6] get rid of block_write_begin_newtrunc Christoph Hellwig
2010-05-31  7:13 ` [PATCH 0/6] first step toward the new truncate sequence Nick Piggin
2010-05-31  7:38   ` Christoph Hellwig
2010-05-31  7:45     ` Nick Piggin
2010-05-31  9:50 ` Boaz Harrosh
2010-05-31 10:17   ` Boaz Harrosh
2010-05-31 13:15     ` Nick Piggin
2010-05-31 13:18       ` Christoph Hellwig
2010-05-31 13:21       ` Boaz Harrosh
2010-06-01 10:07   ` Christoph Hellwig

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=20100530204932.GA21002@lst.de \
    --to=hch@lst.de \
    --cc=jack@suse.cz \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=npiggin@suse.de \
    --cc=viro@zeniv.linux.org.uk \
    /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.