From: Liu Bo <bo.li.liu@oracle.com>
To: lsf-pc@lists.linuxfoundation.org
Cc: linux-fsdevel@vger.kernel.org
Subject: [LSF/MM ATTEND] Attendance request
Date: Sun, 28 Feb 2016 15:16:15 -0800 [thread overview]
Message-ID: <20160228231615.GA29981@localhost.localdomain> (raw)
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
next reply other threads:[~2016-02-28 23:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-28 23:16 Liu Bo [this message]
2016-03-04 14:30 ` [LSF/MM ATTEND] Attendance request David Sterba
2016-03-04 16:53 ` Liu Bo
2016-03-04 16:59 ` Liu Bo
2016-03-04 17:25 ` David Sterba
2016-03-04 18:08 ` Liu Bo
-- strict thread matches above, loose matches on Subject: below --
2016-02-25 20:23 [LSF/MM ATTEND] attendance request Andreas Dilger
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=20160228231615.GA29981@localhost.localdomain \
--to=bo.li.liu@oracle.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=lsf-pc@lists.linuxfoundation.org \
/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).