Dan Magenheimer | 83bc7a7 | 2012-02-15 07:54:19 -0800 | [diff] [blame] | 1 | For this staging driver, RAMster duplicates code from drivers/staging/zcache |
| 2 | then incorporates changes to the local copy of the code. For V5, it also |
| 3 | directly incorporates the soon-to-be-removed drivers/staging/zram/xvmalloc.[ch] |
| 4 | as all testing has been done with xvmalloc rather than the new zsmalloc. |
| 5 | Before RAMster can be promoted from staging, the zcache and RAMster drivers |
| 6 | should be either merged or reorganized to separate out common code. |
| 7 | |
| 8 | Until V4, RAMster duplicated code from fs/ocfs2/cluster, but this made |
| 9 | RAMster incompatible with ocfs2 running in the same kernel and included |
| 10 | lots of code that could be removed. As of V5, the ocfs2 code has been |
| 11 | mined and made RAMster-specific, made to communicate with a userland |
| 12 | ramster-tools package rather than ocfs2-tools, and can co-exist with ocfs2 |
| 13 | both in the same kernel and in userland on the same machine. |