From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-1.0 required=3.0 tests=DKIMWL_WL_MED,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_PASS autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 86D9FC43381 for ; Wed, 20 Feb 2019 18:37:42 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 4F9102146E for ; Wed, 20 Feb 2019 18:37:42 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=plexistor-com.20150623.gappssmtp.com header.i=@plexistor-com.20150623.gappssmtp.com header.b="ooMwg9Ul" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726332AbfBTShl (ORCPT ); Wed, 20 Feb 2019 13:37:41 -0500 Received: from mail-wm1-f66.google.com ([209.85.128.66]:38292 "EHLO mail-wm1-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725842AbfBTShl (ORCPT ); Wed, 20 Feb 2019 13:37:41 -0500 Received: by mail-wm1-f66.google.com with SMTP id v26so7437625wmh.3 for ; Wed, 20 Feb 2019 10:37:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=plexistor-com.20150623.gappssmtp.com; s=20150623; h=to:from:subject:cc:message-id:date:user-agent:mime-version :content-transfer-encoding; bh=2JqivuspCd7MW36rR+owYcUDVPSUUw5vvbF3CFq590E=; b=ooMwg9UlTpTJaaA2VDIv16888PNU8P3a2YYvUcX1oaKZlB6uYd5QQOsgLVsmX+IOuW 7AxKw0TkSk1NZdw2PmHiP321rCBodnDfoPgWZTUyNfRbRA7TLeJZ4NpiE8GUUJKUhmQQ FPBH8k2FB5UFvLi+JT43kCQX69yoBU4dx1fcB2MeH4mKZ07dKfo7+Ym/EPd1V3jh6jjw VbnZKcwzGfGOFMotLPsiCB0ULoTXqhKfrqdcvjtPwVfOYOdd3dI8TBZExKIwu237jN9D lEd3+q0p5LXinfR5RQf8RFyXhD6H4QEo8/GKT1/NTxlxk4hGNnL44NNNGwkPifeJhG4M 1EpA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:to:from:subject:cc:message-id:date:user-agent :mime-version:content-transfer-encoding; bh=2JqivuspCd7MW36rR+owYcUDVPSUUw5vvbF3CFq590E=; b=cVZTBJaDnKaip+TY9s2a497qCdRqCALcqRHW57dDsONGyCQDcxPADd0E7639i+gCd1 ox3EkIxJW1MxVp8KiJFBgKd1cB2XhxBP7QR5z8aQ1VwDzdPGIDWB/TsDYSx5meqvaECu CszDy9cdg7Z6v3DwgDCVqKqnJgjPfuhJtlMQQA67Yv4NNQbfxXS07NaRaVxrDUwF9KeB o93Gvbzan3bozS9NcSRzKRDEB7fHoBjL+2z90rChX+ffL0SniL74nZtHNVQnospMbaCT 4PJEH5lpdXhXsLLskjv3l1lxJAGLsGVtkWDRlG7ehilyGZMojHrlVHiZdw4wNBD4mjC8 7lrA== X-Gm-Message-State: AHQUAuZ1nlpvo++gJ3khrntBQic54XfLhLjQ+hCAcVpYkFHHwh8vzMwC up9f0OMa6DN+ENfZM7zTukm1Jr969bw= X-Google-Smtp-Source: AHgI3IaATDnTS4gcjokxVMyhXHmb22C14SHe9Hqg4a7A6NbzWdRbqoB1QxbWXJu+zR/yGibto8q3ZA== X-Received: by 2002:a7b:c08a:: with SMTP id r10mr7317669wmh.112.1550687859337; Wed, 20 Feb 2019 10:37:39 -0800 (PST) Received: from [10.0.0.5] ([207.232.55.62]) by smtp.googlemail.com with ESMTPSA id z15sm5497102wmi.46.2019.02.20.10.37.37 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 20 Feb 2019 10:37:38 -0800 (PST) To: lsf-pc@lists.linux-foundation.org, linux-fsdevel , Anna Schumaker , Josef Bacik , Ric Wheeler From: Boaz Harrosh Subject: [LSF/MM TOPIC] ZUFS - How to get ZUFS ready for upstream Cc: Boaz Harrosh , Amit Golander Message-ID: <50449f0f-195d-06cf-0a11-5af911dae5ab@plexistor.com> Date: Wed, 20 Feb 2019 20:37:36 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Sender: linux-fsdevel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-fsdevel@vger.kernel.org From: Boaz Harrosh 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