From: Christoph Lameter <cl@linux.com>
To: linux-mm@kvack.org
Cc: lsf-pc@lists.linuxfoundation.org
Subject: [LSF/MM ATTEND]
Date: Wed, 29 Jan 2014 13:03:18 -0600 (CST) [thread overview]
Message-ID: <alpine.DEB.2.10.1401291256090.24216@nuc> (raw)
Would like to attent the MM meeting this year because there are a
number of issues that I am interested in. The large block size is one
thing, then there is persistent memory / on die memory which seems to be
coming with Broadwell and Xeon Phi. Looks like this is going to be managed
using an additional NUMA node which gives rise to a number of interesting
issues.
I have a talk in for the collab summit to talk about NUMA. Could
specialize this even more for the MM summit if there is interest or
talk about issues in the subsystems I maintain (slab and percpu) or about
issues in the things I have worked on in the past (NUMA, page migration,
atomic primitives, vm scaling, vm statistics etc). But just being there is
also enough...
--
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-29 19:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-29 19:03 Christoph Lameter [this message]
2014-01-31 7:21 Greg Thelen
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=alpine.DEB.2.10.1401291256090.24216@nuc \
--to=cl@linux.com \
--cc=linux-mm@kvack.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