From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from aserp1040.oracle.com ([141.146.126.69]:25010 "EHLO aserp1040.oracle.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755085AbcB1XQX (ORCPT ); Sun, 28 Feb 2016 18:16:23 -0500 Date: Sun, 28 Feb 2016 15:16:15 -0800 From: Liu Bo To: lsf-pc@lists.linuxfoundation.org Cc: linux-fsdevel@vger.kernel.org Subject: [LSF/MM ATTEND] Attendance request Message-ID: <20160228231615.GA29981@localhost.localdomain> Reply-To: bo.li.liu@oracle.com MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Sender: linux-fsdevel-owner@vger.kernel.org List-ID: Hi, I'd like to attend the LSF/MM conference this year. I think I can contribute to a few areas that are being discussed this year: - how to provide better information for the filesystem to optimize allocation. - power/failure tests - performance aspects, etc. Besides that, I'd like to talk about the following, - combining overlayfs with btrfs to properly fix overlayfs copy-up slowness. - fragmentation control in Copy-On-Write filesystems. (setting a reasonable large allocation unit and performing RMW, etc?) Since xfs is also going to have reflink, so xfs is also regarded as COW FS, having some generic ideas for this topic would help a lot. - mount individual subvolumes (in btrfs) with different selinux label, this will be useful in container senarios when btrfs being their storage driver. (I've finished the patch for the above selinux label support, but it can ends up with inode leak if it's not used in the container way, which is assuming the top subvolume is always being the last one to unmout.) thanks, -liubo