From: Matthew Wilcox <matthew.r.wilcox@intel.com>
To: linux-ext4@vger.kernel.org, linux-fsdevel@vger.kernel.org
Cc: Matthew Wilcox <matthew.r.wilcox@intel.com>
Subject: [PATCH v3 0/3] Add XIP support to ext4
Date: Tue, 17 Dec 2013 14:18:25 -0500 [thread overview]
Message-ID: <cover.1387307259.git.matthew.r.wilcox@intel.com> (raw)
For v3, we've addressed the problem with unwritten extents that Dave
Chinner pointed out. Rather than testing bh_unwritten() as he suggested,
I opted for checking !buffer_mapped() as block_read_full_page() in
fs/buffer.c does. While I'm in that function I renamed the buffer_head
from 'tmp' to 'bh' to follow normal usage.
I also folded the "ext4: Add xip hole punching" patch into the main
"Add XIP functionality" patch since otherwise we're introducing broken
functionality in the middle of the series.
Matthew Wilcox (2):
Fix XIP fault vs truncate race
xip: Add xip_zero_page_range
Ross Zwisler (1):
ext4: Add XIP functionality
Documentation/filesystems/ext4.txt | 2 +
Documentation/filesystems/xip.txt | 3 ++
fs/Kconfig | 2 +-
fs/ext4/Kconfig | 11 +++++
fs/ext4/Makefile | 1 +
fs/ext4/ext4.h | 4 +-
fs/ext4/file.c | 17 ++++++++
fs/ext4/inode.c | 86 +++++++++++++++++++++++++++-----------
fs/ext4/namei.c | 11 ++++-
fs/ext4/super.c | 36 +++++++++++++++-
fs/ext4/xip.c | 78 ++++++++++++++++++++++++++++++++++
fs/ext4/xip.h | 24 +++++++++++
include/linux/fs.h | 8 ++++
mm/filemap_xip.c | 55 ++++++++++++++++--------
14 files changed, 289 insertions(+), 49 deletions(-)
create mode 100644 fs/ext4/xip.c
create mode 100644 fs/ext4/xip.h
--
1.8.4.rc3
next reply other threads:[~2013-12-17 19:18 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-17 19:18 Matthew Wilcox [this message]
2013-12-17 19:18 ` [PATCH v3 1/3] Fix XIP fault vs truncate race Matthew Wilcox
2013-12-17 19:18 ` [PATCH v3 2/3] xip: Add xip_zero_page_range Matthew Wilcox
2013-12-17 19:18 ` [PATCH v3 3/3] ext4: Add XIP functionality Matthew Wilcox
2013-12-17 22:30 ` [PATCH v3 0/3] Add XIP support to ext4 Dave Chinner
2013-12-18 2:31 ` Matthew Wilcox
2013-12-18 5:01 ` Theodore Ts'o
2013-12-18 14:27 ` Matthew Wilcox
2013-12-19 2:07 ` Theodore Ts'o
2013-12-19 4:12 ` Matthew Wilcox
2013-12-19 4:37 ` Dave Chinner
2013-12-19 5:43 ` Theodore Ts'o
2013-12-19 15:20 ` Matthew Wilcox
2013-12-19 16:17 ` Theodore Ts'o
2013-12-19 17:12 ` Matthew Wilcox
2013-12-19 17:18 ` Theodore Ts'o
2013-12-20 18:17 ` Matthew Wilcox
2013-12-20 19:34 ` Theodore Ts'o
2013-12-20 20:11 ` Matthew Wilcox
2013-12-23 3:36 ` Dave Chinner
2013-12-23 3:45 ` Matthew Wilcox
2013-12-23 4:32 ` Dave Chinner
2013-12-23 6:56 ` Dave Chinner
2013-12-23 14:51 ` Theodore Ts'o
2013-12-23 3:16 ` Dave Chinner
2013-12-24 16:27 ` Matthew Wilcox
2013-12-18 12:33 ` Dave Chinner
2013-12-18 15:22 ` Matthew Wilcox
2013-12-19 0:48 ` Dave Chinner
2013-12-19 1:05 ` Matthew Wilcox
2013-12-19 1:58 ` Dave Chinner
2013-12-19 15:32 ` Matthew Wilcox
2013-12-19 23:46 ` Dave Chinner
2013-12-20 16:45 ` Matthew Wilcox
2013-12-23 4:14 ` Dave Chinner
2013-12-18 18:13 ` Eric Sandeen
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.1387307259.git.matthew.r.wilcox@intel.com \
--to=matthew.r.wilcox@intel.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.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).