- Subject: Re: [RFC/PATCH] zcache/ramster rewrite and promotion
- From: Pekka Enberg <penberg@xxxxxxxxxx>
- Date: Sat, 4 Aug 2012 11:59:04 +0300
- Cc: devel@xxxxxxxxxxxxxxxxxxxx, Seth Jennings <sjenning@xxxxxxxxxxxxxxxxxx>, Konrad Wilk <konrad.wilk@xxxxxxxxxx>, Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>, linux-kernel@xxxxxxxxxxxxxxx, linux-mm@xxxxxxxxx, Minchan Kim <minchan@xxxxxxxxxx>, Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>, Robert Jennings <rcj@xxxxxxxxxxxxxxxxxx>, Nitin Gupta <ngupta@xxxxxxxxxx>
- Delivered-to: devel@xxxxxxxxxxxxxxxxxxxx
- In-reply-to: <b9bee363-321e-409a-bc8e-65ffed8a1dc5@default>
Hi Dan,
On Wed, Aug 1, 2012 at 12:13 AM, Dan Magenheimer
<dan.magenheimer@xxxxxxxxxx> 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
_______________________________________________
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxx
http://driverdev.linuxdriverproject.org/mailman/listinfo/devel
[Video for Linux]
[Mplayer Users]
[Linux USB Devel]
[Linux Audio Users]
[Photos]
[Yosemite Photos]
[Free Singles Community]
[Linux Kernel]
[Linux SCSI]
[XFree86]
[Devices]
[Yosemite Backpacking]