From: Tejun Heo <tj@kernel.org>
To: linux-kernel@vger.kernel.org, fuse-devel@lists.sourceforge.net,
miklos@szeredi.hu, akpm@linux-foundation.org, npiggin@suse.de
Subject: [PATCHSET] FUSE/CUSE: implement direct mmap, take#3
Date: Thu, 18 Jun 2009 18:24:29 +0900 [thread overview]
Message-ID: <1245317073-24000-1-git-send-email-tj@kernel.org> (raw)
Hello,
This is the third take of fuse-implement-direct-mmap patchset. This
patchset implements direct mmap support for FUSE (and CUSE). Each
direct mmap area is backed by anonymous mapping (shmem_file) and the
FUSE server can decide how they are shared.
mmap request is handled in two steps. MMAP first queries the server
whether it wants to share the mapping with an existing one or create a
new one, and if so, with which flags. MMAP_COMMIT notifies the server
the result of mmap and if successful the fd the server can use to
access the mmap region.
Changes from the last take[L] are
* mmap-don-t-assume-f_op-mmap-doesn-t-change-vma.patch was
unnecessary. Dropped and mmap implementation updated accordingly.
* Updated to the current master which now contains CUSE support.
This patchset contains the following patches.
0001-fdtable-export-alloc_fd.patch
0002-FUSE-make-request_wait_answer-wait-for-end-co.patch
0003-FUSE-implement-fuse_req-prep.patch
0004-FUSE-implement-direct-mmap.patch
0001 update exports fdtable for following FUSE changes. 0002-0003
update fuse_req->end() handling and add ->prep(). 0004 implements
direct mmap.
This patchset is on top of
linus#master(1d89b30cc9be41af87881682ec82e2c107849dbe)
and is available in the following git tree.
git://git.kernel.org/pub/scm/linux/kernel/git/tj/misc.git fuse-mmap
diffstat follows.
fs/file.c | 1
fs/fuse/cuse.c | 1
fs/fuse/dev.c | 70 ++++++--
fs/fuse/file.c | 432 +++++++++++++++++++++++++++++++++++++++++++++++++--
fs/fuse/fuse_i.h | 19 ++
include/linux/fuse.h | 47 +++++
6 files changed, 538 insertions(+), 32 deletions(-)
Thanks.
--
tejun
[L] http://thread.gmane.org/gmane.linux.kernel/821839
next reply other threads:[~2009-06-18 9:26 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-18 9:24 Tejun Heo [this message]
2009-06-18 9:24 ` [PATCH 1/4] fdtable: export alloc_fd() Tejun Heo
2009-06-24 4:39 ` Al Viro
2009-06-30 3:05 ` Tejun Heo
2009-06-18 9:24 ` [PATCH 2/4] FUSE: make request_wait_answer() wait for ->end() completion Tejun Heo
[not found] ` <20090623165354.073a61fe.akpm@linux-foundation.org>
2009-06-24 0:04 ` Tejun Heo
2009-06-24 10:02 ` Miklos Szeredi
2009-06-29 16:20 ` Tejun Heo
2009-06-18 9:24 ` [PATCH 3/4] FUSE: implement fuse_req->prep() Tejun Heo
2009-06-23 23:56 ` Andrew Morton
2009-06-24 0:07 ` Tejun Heo
2009-06-18 9:24 ` [PATCH 4/4] FUSE: implement direct mmap Tejun Heo
2009-06-24 0:14 ` Andrew Morton
2009-06-29 16:59 ` Tejun Heo
2009-06-24 10:33 ` Miklos Szeredi
2009-06-29 16:42 ` Tejun Heo
2009-07-02 13:51 ` Miklos Szeredi
2009-07-04 11:14 ` Tejun Heo
2009-07-06 11:41 ` Miklos Szeredi
2009-07-08 23:14 ` Tejun Heo
2009-07-09 10:35 ` Miklos Szeredi
2009-06-18 9:27 ` [PATCH libfuse] implement direct mmap support Tejun Heo
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=1245317073-24000-1-git-send-email-tj@kernel.org \
--to=tj@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=fuse-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=npiggin@suse.de \
/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.