From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from psmtp.com (na3sys010amx139.postini.com [74.125.245.139]) by kanga.kvack.org (Postfix) with SMTP id 1021D6B0068 for ; Sat, 4 Aug 2012 04:59:06 -0400 (EDT) Received: by wibhm2 with SMTP id hm2so244669wib.2 for ; Sat, 04 Aug 2012 01:59:04 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: References: Date: Sat, 4 Aug 2012 11:59:04 +0300 Message-ID: Subject: Re: [RFC/PATCH] zcache/ramster rewrite and promotion From: Pekka Enberg Content-Type: text/plain; charset=ISO-8859-1 Sender: owner-linux-mm@kvack.org List-ID: To: Dan Magenheimer Cc: Seth Jennings , Konrad Wilk , Minchan Kim , Nitin Gupta , Andrew Morton , Robert Jennings , Greg Kroah-Hartman , devel@driverdev.osuosl.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org Hi Dan, On Wed, Aug 1, 2012 at 12:13 AM, Dan Magenheimer wrote: > Ramster does the same thing but manages it peer-to-peer across > multiple systems using kernel sockets. One could argue that > the dependency on sockets makes it more of a driver than "mm" > but ramster is "memory management" too, just a bit more exotic. How do you configure it? Can we move parts of the network protocol under net/ramster or something? Pekka -- 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