Lines Matching refs:backend

41 If a backend chooses, frontswap can be configured as a "writethrough
44 in order to allow the backend to arbitrarily "reclaim" space used to
61 A backend implementation may provide additional metrics.
106 Specifically, the Xen Transcendent Memory backend allows otherwise
125 swap device.  If CONFIG_FRONTSWAP is enabled but no frontswap "backend"
128 AND a frontswap backend registers AND the backend fails every "store"
135 As for space, if CONFIG_FRONTSWAP is enabled AND a frontswap backend
148 backend, such as zcache, must implement policies to carefully (but
154 Let's assume that a frontswap "backend" has registered during
156 frontswap backend has access to some "memory" that is not directly
167 consults with the frontswap backend and if the backend says it does NOT
170 backend is unpredictable to the kernel; it may choose to never accept a
172 page.  But if the backend does accept a page, the data from the page
174 and the backend guarantees the persistence of the data.  In this case,
181 see if the page was earlier accepted by the frontswap backend.  If
182 it was, the page of data is filled from the frontswap backend and
186 So every time the frontswap backend accepts a page, a swap device read
187 and (potentially) a swap device write are replaced by a "frontswap backend
188 store" and (possibly) a "frontswap backend loads", which are presumably much
204 For example, the acceptance of any swap page by the frontswap backend is
207 backend.  In zcache, one cannot know a priori how compressible a page is.
216 required to ensure the dynamicity of the backend and to avoid thorny race
240 can still use frontswap but a backend for such devices must configure
250 is non-compressible and so would take the entire 4K.  But the backend