[lkml]   [2010]   [Feb]   [10]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [fuse-devel] [PATCH] FUSE/CUSE: implement direct mmap support
On Wed, 10 Feb 2010, Goswin von Brederlow wrote:
> Tejun Heo <> writes:
> > Implement FUSE direct mmap support. The server can redirect client
> > mmap requests to any SHMLBA aligned offset in the custom address space
> > attached to the fuse channel. The address space is managed by the
> > server using mmap/munmap(2). The SHMLBA alignment requirement is
> > necessary to avoid cache aliasing issues on archs with virtually
> > indexed caches as FUSE direct mmaps are basically shared memory
> > between clients and the server.
> >
> > The direct mmap address space is backed by pinned kernel pages which
> > are allocated on the first fault either from a client or the server.
> > If used carelessly, this can easily waste and drain memory.
> > Currently, a server must have CAP_SYS_ADMIN to manage dmmap regions by
> > mmapping and munmapping the channel fd.
> Does that mean that for example in unionfs-fuse when a user wants to
> mmap a file I can just mmap the actual underlying file from the real
> filesystem and any read/write access would then shortcut fuse and go
> directly to the real file?

No. It is the /dev/fuse file descriptor that is being mapped to give
access to the "direct mmaped" memory.


 \ /
  Last update: 2010-02-10 09:43    [W:0.074 / U:7.516 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site