From: Boaz Harrosh <openosd@gmail.com>
To: lsf-pc@lists.linux-foundation.org,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Anna Schumaker <Anna.Schumaker@netapp.com>,
Josef Bacik <josef@redhat.com>,
Ric Wheeler <ricwheeler@gmail.com>
Cc: Boaz Harrosh <boazh@netapp.com>,
Amit Golander <Amit.Golander@netapp.com>
Subject: [LSF/MM TOPIC] ZUFS - How to get ZUFS ready for upstream
Date: Sun, 24 Feb 2019 14:47:29 +0200 [thread overview]
Message-ID: <138ffa94-6796-6f76-99d5-370f3f29b9e9@gmail.com> (raw)
From: Boaz Harrosh <boazh@netapp.com>
Hello fellow Linuxers
ZUFS has been proven to be very capable and very fast - though not as fast as I would like
and work is done to still improve on that.
And very stable. Its been in testing and QA labs for a year. And finally has been
released for paying costumers to help them with the extreme workloads they demand.
The release is based on RHEL 7.6. The Kernel + user-mode Server are open source.
The actual FS provider is closed-source.
So its been capable and reliable to be trusted with some type of real user data
and processing.
But is it secure? Is it capable to maintain the Kernel hardening.
I would please like to give a 5 minutes overview of the project. And then
leave the entire talk to discussion and investigation about the different
parts.
I would like to advise with the Linux good folks how to move forward and get
this project forward, to be ready for an upstream Kernel near us?
What do we need to test and prove for this to be considered good enough?
I would like to make a short pitch of why the LSF/MM guys should care about
ZUFS at all.
Well because what is introduced here is a very capable very new way to interface
user-mode from Kernel and/or app-to-app. Which by taking a deep consideration of
modern multi-core, multi-NUMA machines. Enables performance never seen before
from an application server.
We believe Filesystems are only the first to benefit from this and more subsystems
and projects could be extended to use the patterns / code introduced here.
Thanks for listening
Boaz
next reply other threads:[~2019-02-24 12:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-24 12:47 Boaz Harrosh [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-02-20 18:37 [LSF/MM TOPIC] ZUFS - How to get ZUFS ready for upstream Boaz Harrosh
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=138ffa94-6796-6f76-99d5-370f3f29b9e9@gmail.com \
--to=openosd@gmail.com \
--cc=Amit.Golander@netapp.com \
--cc=Anna.Schumaker@netapp.com \
--cc=boazh@netapp.com \
--cc=josef@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=ricwheeler@gmail.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).