From owner-freebsd-hackers@freebsd.org Mon Oct 22 16:23:38 2018 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 767C8103765C for ; Mon, 22 Oct 2018 16:23:38 +0000 (UTC) (envelope-from vijju.singh@gmail.com) Received: from mail-wr1-x42f.google.com (mail-wr1-x42f.google.com [IPv6:2a00:1450:4864:20::42f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id DC9A482C15; Mon, 22 Oct 2018 16:23:37 +0000 (UTC) (envelope-from vijju.singh@gmail.com) Received: by mail-wr1-x42f.google.com with SMTP id q7-v6so17806126wrr.8; Mon, 22 Oct 2018 09:23:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=VDML47pm5YM7SCfXD3NumVvOhzKVXqRsD0XHjhi7Aws=; b=qs5RDFmbVWXg5yE+6fpjomelhtau2+9RAhkhoZdxP81pxegQzhRkOIVnQgO2wZF8kw q2Silp4br5NpZ+F0R2Jz7UAzEIgMrsmXf2d9JeInbtINP/bxsUw8LJYJ4Yf5eOTXvfvn CHylOzuZtjhOm3w5MN1WXyhaKAjDjYtluMi8psI8SKX5nyzl16IPzB1ViY7zkpoC/kyB cuxtg/arkrTdn/DmR9MhGmGkUZ7OZhIFuu7IS7RLN+JPZapXTQrITcDMYIkGVimGIkhy paJLmXm3R0ihkqeOLp4Q/fgEgRItOXNo1lfwTXx2m3fnKe74qWYrMFPyNCjDGg4+DF2U gY0g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=VDML47pm5YM7SCfXD3NumVvOhzKVXqRsD0XHjhi7Aws=; b=TvRd+wo6dlyQqRSMoiAgn0TFvQCLoUbFaipE7/ATlPM4sen2dvBMWWf79NBXGNy4rq F66tQyhJxHe1xhwnNUkCR6JDMkN3GL1vxc1Sy5J3I2tspwO1kMEeoap4zWez0hi1SR+t zo8rkwo0U1RpLIxG8vDTNTPK8dd36KSViGyCCZm7jwjHvGH9ydr42hjdIjpnBMNxpgLO GIrTn+PS67q+RyelO2mV4S8j1gUweibVBE0ODvkRmXODTgu8z7RbGN09JT2vmXHw/kD9 fUzDsM3Z8P9tzOm+Fvj4pm70TEtDr+gOaFuAHvciuvtDHgPtRqRKaizGWpRpMeLyimPQ 7gJw== X-Gm-Message-State: AGRZ1gLyoDp17X2y3SfEbym1fFDxRjG0Uh6wwPIG8fw3vw52xwME+1le WzaSEMR/fIxqT6cMbfik72RdrwQuOluZZFYLHi4sj73O X-Google-Smtp-Source: AJdET5dOmC+v0P7Hu3ahyBQPtX5RAoQ4SUu2PFe1o+4cw2E/6JWLJmoJnsTbeAB2ePUm2INbFiI9RJF97Q5L8VNN6lQ= X-Received: by 2002:a05:6000:108d:: with SMTP id y13mr6143571wrw.226.1540225416278; Mon, 22 Oct 2018 09:23:36 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Vijay Singh Date: Mon, 22 Oct 2018 09:23:17 -0700 Message-ID: Subject: Re: SNIA SDC 2018 recap To: Alan Somers Cc: FreeBSD Hackers Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Oct 2018 16:23:38 -0000 I was there as well Alan :) On Mon, Oct 22, 2018, 9:13 AM Alan Somers wrote: > The SNIA Storage Developers' Conference was held in Santa Clara during the > last week of September. Jim Harris, John Hixon, Nick Principe, Michael > Dexter, and myself attended. As far as FreeBSD goes, here's a summary of > the juiciest bits: > > NVDIMM/PMEM: A lot of companies are still pushing persistent memory > products. They're getting better, but still quite vendor-specific. > Fortunately, there are standardization efforts in place. JEDEC is > standardizing the hardware (NVDIMM-N, NVDIMM-P, NVDIMM-F). Every major > memory company (but not CPU company) is on-board. SNIA is also trying to > standardize a programming model (but not the precise API). Windows and > Linux currently support it, with differences. There will probably be some > additional changes to the model. > https://static.ptbl.co/static/attachments/187585/1537988510.pdf?1537988510 > . iX Systems reported some impressive benchmarks using an NVDIMM as a ZFS > slog device. Several databases are adding pmem support. A few filesystems > have some level of NVDIMM support, and the NOVA filesystem is being written > from the ground up to take full advantage of NVDIMM. For example, > directories are stored as in-memory data structures that never get > serialized. The lesson here is that FreeBSD needs to support the standard > NVDIMM programming model too. > > OpenChannel SSDs: These are SSDs that expose more of their internal > implementation details to the host. Specifically, they rely on the host > for at least part of garbage collection. They also expose their multiple > internal busses to the host, so it can choose how to stripe data across > them. Overall, the programming model is surprisingly similar to that of > SMR hard drives. Unfortunately, the standard is a bit murky. Different > speakers could not even agree on whether there is a standard. This is the > best presentation on the topic: > https://static.ptbl.co/static/attachments/187321/1537829929.pdf?1537829929 > and this is the closest thing there is to a standard ATM: > https://openchannelssd.readthedocs.io/en/latest/ . The lesson here is > that > FreeBSD needs to plumb these devices' properties up to userland and perhaps > expose them in zonectl(8) (easy) and add filesystem support (very hard). > > NVMe: If there were an award for most popular buzzword, it would've gone to > "NVMe". Everybody and their mother had something to say about it. But I > personally paid little attention (except as regards OpenChannel). > > Seagate dual-actuator hard drives: Seagate is coming out with hard drives > that pack two servos into a single case. Each servo can access half of the > platters. The drive reports each servo as a separate LUN to the host. > There is little FreeBSD needs to do here. To make zfsd(8) work correctly, > we should add lun info to the drives' physical path strings. And it might > be nice if zpool(8) prevented the user from adding both LUNs of the same > physical drive to the same RAID group. But that's arguably out of our > domain. > > SPDK: The storage-plane developer's kit is like Intel's version of Netmap, > but for storage. It's a say for userland programs to access storage > devices directly, bypassing the kernel. The benefits are negligible for > spinning media, but can be significant for fast NVMe drives. SPDK has > multiple backends for different I/O controllers, including some that are > kernel-based. Notably lacking is a POSIX AIO backend. That's probably the > biggest gap in its FreeBSD support. > > iX Systems wrote a blog post about the conference, too. It covers > Swordfish and Samba, two topics I ignored. > > https://www.ixsystems.com/blog/snia-sdc-2018/ > > -Alan > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" >