Lines Matching full:backend

63 A backend implementation may provide additional metrics.
107 Specifically, the Xen Transcendent Memory backend allows otherwise
126 swap device.  If CONFIG_FRONTSWAP is enabled but no frontswap "backend"
129 AND a frontswap backend registers AND the backend fails every "store"
136 As for space, if CONFIG_FRONTSWAP is enabled AND a frontswap backend
149 backend, such as zcache, must implement policies to carefully (but
155 Let's assume that a frontswap "backend" has registered during
157 frontswap backend has access to some "memory" that is not directly
168 consults with the frontswap backend and if the backend says it does NOT
171 backend is unpredictable to the kernel; it may choose to never accept a
173 page.  But if the backend does accept a page, the data from the page
175 and the backend guarantees the persistence of the data.  In this case,
182 see if the page was earlier accepted by the frontswap backend.  If
183 it was, the page of data is filled from the frontswap backend and
187 So every time the frontswap backend accepts a page, a swap device read
188 and (potentially) a swap device write are replaced by a "frontswap backend
189 store" and (possibly) a "frontswap backend loads", which are presumably much
205 For example, the acceptance of any swap page by the frontswap backend is
208 backend.  In zcache, one cannot know a priori how compressible a page is.
217 required to ensure the dynamicity of the backend and to avoid thorny race
241 can still use frontswap but a backend for such devices must configure
251 is non-compressible and so would take the entire 4K.  But the backend