From: Zhi Yong Wu <zwu.kernel@gmail.com>
To: lsf-pc@lists.linux-foundation.org
Cc: "linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
mgorman@suse.de, Christoph Hellwig <hch@infradead.org>,
"Theodore Ts'o" <tytso@mit.edu>
Subject: [LSF/MM ATTEND] Filesystems - VFS, ext4, xfs, btrfs, etc
Date: Mon, 1 Dec 2014 12:32:05 +0800 [thread overview]
Message-ID: <CAEH94Lh_auk+H6M+G6JomvqVqbg8GGAcZHi3-xnH0O4274_btw@mail.gmail.com> (raw)
HI,
HI, folks
I'd like to attend LSF/MM summit, been very interested in the
discussion related to VFS, ext4, xfs, btrfs, and memory management;
and would like to discuss some FS perf stuff with others.
--
Regards,
Zhi Yong Wu
next reply other threads:[~2014-12-01 4:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-01 4:32 Zhi Yong Wu [this message]
2014-12-01 8:54 ` [Lsf-pc] [LSF/MM ATTEND] Filesystems - VFS, ext4, xfs, btrfs, etc Jan Kara
2014-12-01 9:35 ` Zhi Yong Wu
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=CAEH94Lh_auk+H6M+G6JomvqVqbg8GGAcZHi3-xnH0O4274_btw@mail.gmail.com \
--to=zwu.kernel@gmail.com \
--cc=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=mgorman@suse.de \
--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).