From: Boaz <boazharrosh@gmail.com>
To: ksummit-discuss@lists.linuxfoundation.org
Subject: [Ksummit-discuss] [TECH TOPIC] Linux Plumbers 2018: ZUFS - Zero Copy User-Mode FileSystem - One year Later
Date: Tue, 2 Oct 2018 19:10:33 +0300 [thread overview]
Message-ID: <CAPvSq70QMfhF1kwKDVVz14pLP73XvVoJ8DJU7FRciaUg5zxYUA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 845 bytes --]
Linux Plumbers 2018: ZUFS - Zero Copy User-Mode FileSystem - One year Later
One year after its inception there are real hardened FSs. Real performance
measurements. and many innovative fixtures. But is it ready for upstream?
Few highlights:
- ALL VFS api working including dax, mmap IOCTL xattrs ACLs ....
(Missing quota)
- IO API changed (From last year)
- Support for ASYNC operations
- Support for both pmem and regular block devices
- Support for private memory pools
- ZTs multy-channel and dynamic channel allocation
- And many more ...
In the talk I will give a short architectural and functional overview.
Then will go over some of the leftover challenges.
And finally hope to engage in an open discussion of how this project should
move
forward to be accepted into the Kernel, gain more users and FS
implementations.
Cheers
Boaz
[-- Attachment #2: Type: text/html, Size: 1194 bytes --]
reply other threads:[~2018-10-02 16:10 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=CAPvSq70QMfhF1kwKDVVz14pLP73XvVoJ8DJU7FRciaUg5zxYUA@mail.gmail.com \
--to=boazharrosh@gmail.com \
--cc=ksummit-discuss@lists.linuxfoundation.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).