From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-yh0-f41.google.com (mail-yh0-f41.google.com [209.85.213.41]) by kanga.kvack.org (Postfix) with ESMTP id 9FCF66B0031 for ; Wed, 15 Jan 2014 23:41:24 -0500 (EST) Received: by mail-yh0-f41.google.com with SMTP id i7so69209yha.0 for ; Wed, 15 Jan 2014 20:41:24 -0800 (PST) Received: from mail-pd0-x235.google.com (mail-pd0-x235.google.com [2607:f8b0:400e:c02::235]) by mx.google.com with ESMTPS id v3si8132902yhv.244.2014.01.15.20.41.23 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 15 Jan 2014 20:41:23 -0800 (PST) Received: by mail-pd0-f181.google.com with SMTP id p10so2071285pdj.12 for ; Wed, 15 Jan 2014 20:41:22 -0800 (PST) MIME-Version: 1.0 Date: Thu, 16 Jan 2014 12:41:22 +0800 Message-ID: Subject: [LSF/MM ATTEND] Persistent memory, per-bdi cgroup, scsi From: Sha Zhengju Content-Type: text/plain; charset=ISO-8859-1 Sender: owner-linux-mm@kvack.org List-ID: To: lsf-pc@lists.linux-foundation.org Cc: "linux-mm@kvack.org" , linux-scsi@vger.kernel.org Hello, I'd like to attend LSF/MM 2014. Whether expose persitent memory directly to the CPU or hide it behind a PCIe IO controller, I'm interested to learn/discuss the short and long term mechanisms that exploiting its benefits of fast, bytes-addressable, non-volatile. Last year I mainly worked on memcg, and recently I begin to look at io stack layers for some developments, such as blk-mq, device mapper, scsi etc. I'm also interested in related topics. -- Thanks, Sha -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org