From: Miklos Szeredi <miklos@szeredi.hu>
To: linux-fsdevel@vger.kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Cc: jens.axboe@oracle.com, akpm@linux-foundation.org,
torvalds@linux-foundation.org
Subject: [RFC PATCH 0/6] fuse: implement zero copy read
Date: Wed, 28 Apr 2010 18:16:36 +0200 [thread overview]
Message-ID: <20100428161636.272097923@szeredi.hu> (raw)
This series implements splice(2) to the fuse device. With this it's
possible to move pages directly into the page cache of the fuse
filesystem without ever having to copy the contents.
The next series will implement splicing from the fuse device for zero
copy write operations.
Testing shows improved bandwidth and reduced system time (as
expected). However there's still some overhead in shuffling pages
between caches. Further improvements could be achieved by
- implementing replace_page_cache_page() which atomically removes an
old page and replaces it with a new one
- implementing splice a-la O_DIRECT which, instead of populating the
page cache, would just send/receive data directly in pipe buffers.
Comments?
Thanks,
Miklos
--
next reply other threads:[~2010-04-28 16:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-28 16:16 Miklos Szeredi [this message]
2010-04-28 16:16 ` [RFC PATCH 1/6] mm: export lru_cache_add_*() to modules Miklos Szeredi
2010-04-28 16:16 ` [RFC PATCH 2/6] mm: export remove_from_page_cache() " Miklos Szeredi
2010-04-28 16:16 ` [RFC PATCH 3/6] fuse: use get_user_pages_fast() Miklos Szeredi
2010-04-28 16:16 ` [RFC PATCH 4/6] fuse: get page reference for readpages Miklos Szeredi
2010-04-28 16:16 ` [RFC PATCH 5/6] fuse: support splice() writing to fuse device Miklos Szeredi
2010-04-28 16:16 ` [RFC PATCH 6/6] fuse: allow splice to move pages Miklos Szeredi
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=20100428161636.272097923@szeredi.hu \
--to=miklos@szeredi.hu \
--cc=akpm@linux-foundation.org \
--cc=jens.axboe@oracle.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®