---

yaml
---
r: 304734
b: refs/heads/master
c: 00bf19f
h: refs/heads/master
v: v3

[refs]

@@ -1,2 +1,2 @@
 ---
-refs/heads/master: 1894a253db97059bc299b834b76f665bc6586b1d
+refs/heads/master: 00bf19f31527f73caf1e9e1d8104404961ebe798

trunk/drivers/staging/ramster/Kconfig

@@ -1,8 +1,8 @@
 config RAMSTER
 	bool "Cross-machine RAM capacity sharing, aka peer-to-peer tmem"
-	depends on (CLEANCACHE || FRONTSWAP) && CONFIGFS_FS=y && !ZCACHE && CRYPTO=y && !HIGHMEM && NET
-	select ZSMALLOC
-	select CRYPTO_LZO
+	depends on (CLEANCACHE || FRONTSWAP) && CONFIGFS_FS=y && !ZCACHE && !XVMALLOC && !HIGHMEM && NET
+	select LZO_COMPRESS
+	select LZO_DECOMPRESS
 	default n
 	help
 	  RAMster allows RAM on other machines in a cluster to be utilized

trunk/drivers/staging/ramster/Makefile

@@ -1 +1 @@
-obj-$(CONFIG_RAMSTER)	+=	zcache-main.o tmem.o r2net.o cluster/
+obj-$(CONFIG_RAMSTER)	+=	zcache-main.o tmem.o r2net.o xvmalloc.o cluster/

trunk/drivers/staging/ramster/TODO

@@ -1,5 +1,7 @@
 For this staging driver, RAMster duplicates code from drivers/staging/zcache
-then incorporates changes to the local copy of the code.
+then incorporates changes to the local copy of the code.  For V5, it also
+directly incorporates the soon-to-be-removed drivers/staging/zram/xvmalloc.[ch]
+as all testing has been done with xvmalloc rather than the new zsmalloc.
 Before RAMster can be promoted from staging, the zcache and RAMster drivers
 should be either merged or reorganized to separate out common code.