From: Matthew Wilcox <matthew.r.wilcox@intel.com>
To: linux-fsdevel@vger.kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Cc: Matthew Wilcox <matthew.r.wilcox@intel.com>, willy@linux.intel.com
Subject: [PATCH v2 0/6] Page I/O
Date: Sun, 23 Mar 2014 15:08:22 -0400 [thread overview]
Message-ID: <cover.1395593198.git.matthew.r.wilcox@intel.com> (raw)
Page I/O allows us to read/write pages to storage without allocating any
memory (in particular, it avoids allocating a BIO). This is nice for
the purposes of swap and reduces overhead for fast storage devices. The
downside is that it removes all batching from the I/O path, potentially
sending dozens of commands for a large I/O instead of just one.
This iteration of the Page I/O patchset has been tested with xfstests
on ext4 on brd, and there are no unexpected failures.
Changes since v1:
- Rebased to 3.14-rc7
- Separate out the clean_buffers() refactoring into its own patch
- Change the page_endio() interface to take an error code rather than
a boolean 'success'. All of its callers prefer this (and my earlier
patchset got this wrong in one caller).
- Added kerneldoc to bdev_read_page() and bdev_write_page()
- bdev_write_page() now does less on failure. Since its two customers
(swap and mpage) want to do different things to the page flags on
failure, let them.
- Drop the virtio_blk patch, since I don't think it should be included
Keith Busch (1):
NVMe: Add support for rw_page
Matthew Wilcox (5):
Factor clean_buffers() out of __mpage_writepage()
Factor page_endio() out of mpage_end_io()
Add bdev_read_page() and bdev_write_page()
swap: Use bdev_read_page() / bdev_write_page()
brd: Add support for rw_page
drivers/block/brd.c | 10 ++++
drivers/block/nvme-core.c | 129 +++++++++++++++++++++++++++++++++++++---------
fs/block_dev.c | 63 ++++++++++++++++++++++
fs/mpage.c | 84 +++++++++++++++---------------
include/linux/blkdev.h | 4 ++
include/linux/pagemap.h | 2 +
mm/filemap.c | 25 +++++++++
mm/page_io.c | 23 ++++++++-
8 files changed, 273 insertions(+), 67 deletions(-)
--
1.9.0
--
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 reply other threads:[~2014-03-23 19:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-23 19:08 Matthew Wilcox [this message]
2014-03-23 19:08 ` [PATCH v2 1/6] Factor clean_buffers() out of __mpage_writepage() Matthew Wilcox
2014-03-23 19:08 ` [PATCH v2 2/6] Factor page_endio() out of mpage_end_io() Matthew Wilcox
2014-03-23 19:08 ` [PATCH v2 3/6] Add bdev_read_page() and bdev_write_page() Matthew Wilcox
2014-03-23 19:08 ` [PATCH v2 4/6] swap: Use bdev_read_page() / bdev_write_page() Matthew Wilcox
2014-03-23 19:08 ` [PATCH v2 5/6] NVMe: Add support for rw_page Matthew Wilcox
2014-03-23 19:08 ` [PATCH v2 6/6] brd: " Matthew Wilcox
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=cover.1395593198.git.matthew.r.wilcox@intel.com \
--to=matthew.r.wilcox@intel.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=willy@linux.intel.com \
/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).