public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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: implement direct mmap, take#2
Date: Tue, 14 Apr 2009 11:04:17 +0900	[thread overview]
Message-ID: <1239674662-31318-1-git-send-email-tj@kernel.org> (raw)

Hello, Miklos, Nick, Andrew.

This is the second 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

* 0003-FUSE-don-t-let-fuse_req-end-put-the-base-referen.patch was
  merged and thus dropped from this series.

* Updated to the current master + implement-cuse, take#3.

This patchset contains the following patches.

  0001-mmap-don-t-assume-f_op-mmap-doesn-t-change-vma.patch
  0002-fdtable-export-alloc_fd.patch
  0003-FUSE-make-request_wait_answer-wait-for-end-co.patch
  0004-FUSE-implement-fuse_req-prep.patch
  0005-FUSE-implement-direct-mmap.patch

0001-0002 update mm and fdtable for following FUSE changes.  0003-0004
update fuse_req->end() handling and add ->prep().  0005 implements
direct mmap.

Nick, Andrew, can you guys please review and ack 0001-0002?

This patchset is on top of

  linus#master(80a04d3f2f94fb68b5df05e3ac6697130bc3467a)
+ [1] implement-cuse patchset, take#3

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       |  424 +++++++++++++++++++++++++++++++++++++++++++++++++--
 fs/fuse/fuse_i.h     |   19 ++
 include/linux/fuse.h |   47 +++++
 mm/mmap.c            |    1 
 7 files changed, 533 insertions(+), 30 deletions(-)

Thanks.

--
tejun

[L] http://thread.gmane.org/gmane.comp.file-systems.fuse.devel/7212
[1] http://thread.gmane.org/gmane.comp.file-systems.fuse.devel/7705

             reply	other threads:[~2009-04-14  2:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-14  2:04 Tejun Heo [this message]
2009-04-14  2:04 ` [PATCH 1/5] mmap: don't assume f_op->mmap() doesn't change vma->vm_file Tejun Heo
2009-04-14 19:59   ` Hugh Dickins
2009-04-15  2:22     ` Tejun Heo
2009-04-15  4:13   ` Tejun Heo
2009-04-14  2:04 ` [PATCH 2/5] fdtable: export alloc_fd() Tejun Heo
2009-04-14  2:04 ` [PATCH 3/5] FUSE: make request_wait_answer() wait for ->end() completion Tejun Heo
2009-04-14  2:04 ` [PATCH 4/5] FUSE: implement fuse_req->prep() Tejun Heo
2009-04-14  2:04 ` [PATCH 5/5] FUSE: implement direct mmap Tejun Heo
2009-04-15  4:14   ` [PATCH UPDATED] " 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=1239674662-31318-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox