From: Wanpeng Li <liwanp@linux.vnet.ibm.com>
To: lsf-pc@lists.linux-foundation.org
Cc: linux-mm@kvack.org, linux-fsdevel@vger.kernel.org
Subject: [LSF/MM ATTEND] Memory management
Date: Sun, 5 Jan 2014 09:34:04 +0800 [thread overview]
Message-ID: <52c8b696.641b440a.0b9e.fffff0f5SMTPIN_ADDED_BROKEN@mx.google.com> (raw)
Hi,
I would like to attend LSF/MM summit. I'm interested in discussion of sched/numa,
huge pages, memory compression, memory failure, scalability of memory management
subsystem.
Last year I did some work to improve zcache support zero-filled pages and
fix bugs/regressions of many components in memory subsystem.
--
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: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next reply other threads:[~2014-01-05 1:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-05 1:34 Wanpeng Li [this message]
2014-01-10 17:14 Vlastimil Babka
2014-01-13 1:48 Joonsoo Kim
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=52c8b696.641b440a.0b9e.fffff0f5SMTPIN_ADDED_BROKEN@mx.google.com \
--to=liwanp@linux.vnet.ibm.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lsf-pc@lists.linux-foundation.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