linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Theodore Ts'o <tytso@mit.edu>,
	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
Subject: Re: [LSF/MM TOPIC] Lightning round?
Date: Thu, 25 Apr 2019 20:39:55 -0600	[thread overview]
Message-ID: <cf2c4c2b-678a-bda9-bcee-7dd28894e53d@kernel.dk> (raw)
In-Reply-To: <20190425211906.GH4739@mit.edu>

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


  reply	other threads:[~2019-04-26  2:40 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-25 20:00 [LSF/MM] Preliminary agenda ? Anyone ... anyone ? Bueller ? Jerome Glisse
2019-04-25 20:03 ` Jens Axboe
2019-04-25 21:19   ` [LSF/MM TOPIC] Lightning round? Theodore Ts'o
2019-04-26  2:39     ` Jens Axboe [this message]
2019-04-26  5:20     ` Michal Hocko
2019-04-27 15:55   ` [LSF/MM] Preliminary agenda ? Anyone ... anyone ? Bueller ? Vlastimil Babka
2019-04-29 10:46     ` Martin K. Petersen
2019-04-29 11:31       ` [Lsf] " James Bottomley
2019-04-29 11:36         ` Martin K. Petersen
2019-04-29 12:17           ` James Bottomley
2019-04-29 12:31             ` Martin K. Petersen
2019-04-30 16:03           ` Jonathan Adams
2019-04-29 23:54   ` Scheduling conflicts Matthew Wilcox
2019-04-30 10:11     ` Michal Hocko

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=cf2c4c2b-678a-bda9-bcee-7dd28894e53d@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lsf-pc@lists.linux-foundation.org \
    --cc=tytso@mit.edu \
    /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).