From: Sagi Manole <sagi@plexistor.com>
To: lsf-pc@lists.linux-foundation.org,
Josef Bacik <josef@toxicpanda.com>,
Amir Goldstein <amir73il@gmail.com>,
Boaz Harrosh <boazh@netapp.com>,
boaz@plexistor.com
Cc: linux-fsdevel@vger.kernel.org,
Amit Golander <amit.golander@netapp.com>,
Miklos Szeredi <miklos@szeredi.hu>,
sagi.manole@netapp.com
Subject: [LSF/MM/BPF TOPIC] ZUFS: going side-by-side with FUSE
Date: Wed, 12 Feb 2020 16:59:20 +0200 [thread overview]
Message-ID: <20200212145920.18832-1-sagi.manole@netapp.com> (raw)
From: sagi.manole@netapp.com
[Talk by Sagi Manole && Boaz Harrosh]
Hi everyone,
We would like to present the latest updates on the ZUFS project. Particularly,
We would like to talk about how ZUFS provides infrastructures for the user-space
filesystem to execute ultra low-latency IO, enable for smart auto-tiering with
a-synchronous calls to the user space filesystem, take snapshots and other
dedicated ioctls, support for mmap on COWed files and more. We would also like
to present pmfs2, a filesystem for persistent memory in user-space via ZUFS.
The work on user-space pmfs2 is derived from now-discontinued work of in-kernel
pmfs filesystem (namely, using a radix-tree for file's mapping). The github for
pmfs2 is:
https://github.com/sagimnl/pmfs2
We would like discuss the challenges we face in pushing ZUFS upstream. What does
it take for ZUFS to get accepted upstream? We would also like to discuss
the differences between ZUFS and FUSE, in what they resemble and the many ways
they are different.
Thank you all,
Sagi & Boaz
reply other threads:[~2020-02-12 14:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20200212145920.18832-1-sagi.manole@netapp.com \
--to=sagi@plexistor.com \
--cc=amir73il@gmail.com \
--cc=amit.golander@netapp.com \
--cc=boaz@plexistor.com \
--cc=boazh@netapp.com \
--cc=josef@toxicpanda.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=miklos@szeredi.hu \
--cc=sagi.manole@netapp.com \
/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).