Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp156273yba; Thu, 25 Apr 2019 20:17:06 -0700 (PDT) X-Google-Smtp-Source: APXvYqytrXLdosIwdhXSEidedbCdAYrEDV8puS6xfdqwtQ45SiN0dE9PBOuY29A0jS05IBnSCgI6 X-Received: by 2002:a62:b612:: with SMTP id j18mr45031004pff.124.1556248626200; Thu, 25 Apr 2019 20:17:06 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1556248626; cv=none; d=google.com; s=arc-20160816; b=qo8NZdfdhgA/luuoshLFONM2IV+N4YjBzvCkgDg8zp9cdjpHnF7GA0BjYXwV42fDbH lo1QK4rrdOdn5nAbC4jxboA9+VGsFdMiB4l4FIiW9QoJw98UBKpNd8EPo66Z2mIElJfe FMRWKD3GuTiXGqP/obex27WnRchLGb9Z1xz3X0BhYgg1cE4Das/recHwnuE6BpNLsXNT DxQSidCSuWmzLbY5674EssL1yVwUyJ6KUqRUivmP1wGuKEE80jyzdUYciJkuGdpOIvf+ zhXW9kSwjuMVysdW18VjHSHRlkeWhK6dhHdn59uce3ugiLJW5teC8XQBvS9bufCLwfFh gpmg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:to:subject:dkim-signature; bh=VO3iBFMkWhmrJrV24wpgxspECFNCTyofN0BzMsoUTLQ=; b=FhEUtWqYS4ZHRYroCgeq1drXIEru5o0e1VUEwPNRZ7QPNoA88T6rjnu5lk/Q6lcSob Yy5+iQ8mqWbFqnidcRKxt9mkVOGF9Z0oL54ppXuZrsJGrN6SQ5thxQegxdbWo7Eza9GK NtUjBvqohWNsSwHt4Xd0O+FKFmthRp0i9JT09StSbbhtsPPmI4npVDgcaxgncSYMncSk 0bQDdM+fzz2Y25BgOz6A/LC3TfwQhepjrf0fptKka/TpgkS3DltYrZXdyyszWJ8kPbvd +jkCG1DIsWB3IwVX1D0q9rlLw4YPiA0ZMdk5ovoKq5T+vSfxeMd2GzYB0ElNqyMgo0w5 MdZw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel-dk.20150623.gappssmtp.com header.s=20150623 header.b=LLcbJytR; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id 1si25562889plu.320.2019.04.25.20.16.48; Thu, 25 Apr 2019 20:17:06 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel-dk.20150623.gappssmtp.com header.s=20150623 header.b=LLcbJytR; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729376AbfDZCkB (ORCPT + 99 others); Thu, 25 Apr 2019 22:40:01 -0400 Received: from mail-pl1-f195.google.com ([209.85.214.195]:44024 "EHLO mail-pl1-f195.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728517AbfDZCj7 (ORCPT ); Thu, 25 Apr 2019 22:39:59 -0400 Received: by mail-pl1-f195.google.com with SMTP id n8so757276plp.10 for ; Thu, 25 Apr 2019 19:39:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel-dk.20150623.gappssmtp.com; s=20150623; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=VO3iBFMkWhmrJrV24wpgxspECFNCTyofN0BzMsoUTLQ=; b=LLcbJytR27KzYvODS/mG8EoR/6HefQiMUIVwP3LP27thQ7cSxfvw637TF9QubMQB/G gNdKVY9Ohe6zolUH3G9KKkoCqddapgRAYzQUQma9W4SKsZi6dpC0/E3DugJW7YIrJrNL Ipb855ozjGSuuY96EsxTDP98p+pkiXoj+DaB8lS0+TBjKGeG5bLN5is9tbQ8LY4nLh2p 11gTllvu4bVXmrltM7J0yT1NTMDxSwEhmU9g+l40ydLVx6RxbsS4HQtIdN7Cm8JKglRk iY1CbEgf0AUKw9F1v2LnFXdRFt0s+azuUJp9e1CffftnwJ/ypp16Na/T4pkjBN4y1ly7 Arfg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=VO3iBFMkWhmrJrV24wpgxspECFNCTyofN0BzMsoUTLQ=; b=rmAuY+JIFWjpMSkbgGyYETJIjdBnXwkMvmJnXRPTY3yIwBLCY7TdrCJQFOtD5fMl7s cmI5rm8MwATVHShXbPdcf3bDfevTRJ+cT77eW7O/LqdMPWtiLmtLrtl7WLqXURZGMVS7 GSAhysNXr45tb00I2WGg8WBSm5pkpxmr6PRDZi6VN8BmJKDhKXi9X6KFxeikW0QUud28 o/Ke9hvZjosOpgVhVoPadmhNGQ0AEfXleabh79efodus3Dbr2KVpbVar8H5MN4bHcMOW yq/1fHp//ICfkVfuMwB1rzepqPBWnBVRLOuO1YATHGndQYPoKt71Qeh5PXa633hrsl0R Sn6A== X-Gm-Message-State: APjAAAVDLKzVoTGXa8xhlEHg884iqgeUabukXJOEC+YEBlzpEIF9he9j RYMf5/Tdwi7qh4eNWvaMsWNHBrhck+4bMg== X-Received: by 2002:a17:902:bb90:: with SMTP id m16mr5819205pls.340.1556246398081; Thu, 25 Apr 2019 19:39:58 -0700 (PDT) Received: from [192.168.1.121] (66.29.188.166.static.utbb.net. [66.29.188.166]) by smtp.gmail.com with ESMTPSA id b19sm30534749pgb.51.2019.04.25.19.39.56 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 25 Apr 2019 19:39:57 -0700 (PDT) Subject: Re: [LSF/MM TOPIC] Lightning round? To: Theodore Ts'o , lsf-pc@lists.linux-foundation.org, linux-mm@kvack.org, linux-fsdevel@vger.kernel.org, linux-block@vger.kernel.org, linux-kernel@vger.kernel.org References: <20190425200012.GA6391@redhat.com> <83fda245-849a-70cc-dde0-5c451938ee97@kernel.dk> <20190425211906.GH4739@mit.edu> From: Jens Axboe Message-ID: Date: Thu, 25 Apr 2019 20:39:55 -0600 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1 MIME-Version: 1.0 In-Reply-To: <20190425211906.GH4739@mit.edu> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 4/25/19 3:19 PM, Theodore Ts'o wrote: > On Thu, Apr 25, 2019 at 02:03:34PM -0600, Jens Axboe wrote: >> >> which also includes a link to the schedule. Here it is: >> >> https://docs.google.com/spreadsheets/d/1Z1pDL-XeUT1ZwMWrBL8T8q3vtSqZpLPgF3Bzu_jejfk > > It looks like there are still quite a few open slots on Thursday? > Could we perhaps schedule a session for lightning talks? Yes good idea, I've added it. Like previous years, I imagine the schedule will remain fluid, both as we go into the conference, but also during. So we can always add and/or move things around. > I've got at least one thing that I'm hoping to be able to plug as a > lightning round topic. Folks may remember that a year or two ago I > had given an LSF/MM talk about changes to the block layer to support > inline encryption engines[1] (where the data gets encrypted/decrypted > between the DMA engine and the storage device, typically EMCC/UFS > flash). > > [1] https://marc.info/?l=linux-fsdevel&m=148190956210784&w=2 > > Between the Android team really trying to get aligned with upstream, > and multiple SOC vendors interested in providing inline encryption > support in hardware, we (finally) have a few engineers who have been > on implementing this design for the past few months. If all goes > well, hopefully RFC patches will be published on linux-block, > linux-fsdevel, and linux-fscrypto by early next week. Assuming this > happens on schedule, it would be perfect for a lightning talk, with > the goal of commending this patch series for feedback. Agree -- Jens Axboe