linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	linux-fsdevel@vger.kernel.org
Subject: [GIT PULL] fs meta data unmap
Date: Wed, 14 Dec 2016 15:54:19 -0700	[thread overview]
Message-ID: <db91490b-dcfb-983b-52be-265e842dcf0e@kernel.dk> (raw)

Hi Linus,

A series from Jan Kara, providing a more efficient way for unmapping
meta data from in the buffer cache than doing it block-by-block. Provide
a general helper that existing callers can use.

Please pull!


  git://git.kernel.dk/linux-block.git for-4.10/fs-unmap


----------------------------------------------------------------
Jan Kara (6):
      fs: Provide function to unmap metadata for a range of blocks
      direct-io: Use clean_bdev_aliases() instead of handmade iteration
      ext4: Use clean_bdev_aliases() instead of iteration
      ext2: Use clean_bdev_aliases() instead of iteration
      fs: Add helper to clean bdev aliases under a bh and use it
      fs: Remove unmap_underlying_metadata

 fs/buffer.c                 | 104 +++++++++++++++++++++++++++++++-------------
 fs/direct-io.c              |  28 +++---------
 fs/ext2/inode.c             |   9 ++--
 fs/ext4/extents.c           |  13 +-----
 fs/ext4/inode.c             |  18 +++-----
 fs/ext4/page-io.c           |   2 +-
 fs/mpage.c                  |   3 +-
 fs/ntfs/aops.c              |   2 +-
 fs/ntfs/file.c              |   5 +--
 fs/ocfs2/aops.c             |   2 +-
 fs/ufs/balloc.c             |   3 +-
 fs/ufs/inode.c              |   3 +-
 include/linux/buffer_head.h |   7 ++-
 13 files changed, 104 insertions(+), 95 deletions(-)

-- 
Jens Axboe

                 reply	other threads:[~2016-12-14 22:54 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=db91490b-dcfb-983b-52be-265e842dcf0e@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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).