From: Greg KH <gregkh@linuxfoundation.org>
To: "Harrosh, Boaz" <Boaz.Harrosh@netapp.com>
Cc: "ksummit-discuss@lists.linuxfoundation.org"
<ksummit-discuss@lists.linuxfoundation.org>
Subject: Re: [Ksummit-discuss] [TECH TOPIC] ZUFS - Zero Copy User-Mode FileSystem - One year Later
Date: Wed, 3 Oct 2018 04:06:44 -0700 [thread overview]
Message-ID: <20181003110644.GA12451@kroah.com> (raw)
In-Reply-To: <MWHPR06MB2896E4C6CE916007BCB66305EEE90@MWHPR06MB2896.namprd06.prod.outlook.com>
On Wed, Oct 03, 2018 at 09:35:54AM +0000, Harrosh, Boaz wrote:
> 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.
Why wouldn't this be better discussed at the file-system-specific
conference? Or have you already done that this year?
thanks,
greg k-h
next prev parent reply other threads:[~2018-10-03 11:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-03 9:35 Harrosh, Boaz
2018-10-03 11:06 ` Greg KH [this message]
2018-10-03 12:46 ` Harrosh, Boaz
2018-10-08 7:46 ` Boaz Harrosh
2018-10-08 13:47 ` Greg KH
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=20181003110644.GA12451@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Boaz.Harrosh@netapp.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