From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-qc0-f173.google.com (mail-qc0-f173.google.com [209.85.216.173]) by kanga.kvack.org (Postfix) with ESMTP id 4D7EA6B0031 for ; Wed, 29 Jan 2014 14:03:22 -0500 (EST) Received: by mail-qc0-f173.google.com with SMTP id i8so3335421qcq.4 for ; Wed, 29 Jan 2014 11:03:22 -0800 (PST) Received: from qmta14.emeryville.ca.mail.comcast.net (qmta14.emeryville.ca.mail.comcast.net. [2001:558:fe2d:44:76:96:27:212]) by mx.google.com with ESMTP id i33si2419726qgf.130.2014.01.29.11.03.21 for ; Wed, 29 Jan 2014 11:03:21 -0800 (PST) Date: Wed, 29 Jan 2014 13:03:18 -0600 (CST) From: Christoph Lameter Subject: [LSF/MM ATTEND] Message-ID: Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-mm@kvack.org List-ID: To: linux-mm@kvack.org Cc: lsf-pc@lists.linuxfoundation.org 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: email@kvack.org