Lines Matching full:backend

57  * backend portions of the XenStore, following the XenBus convention.
77  *                            Backend XenBus Nodes
80  *------------------ Backend Device Identification (PRIVATE) ------------------
123  *      Therefore this option gives the backend permission to use
130  *      which it is relevant.  A backend which knows that it is not
133  *      This option doesn't require a backend to use O_DIRECT, so it
142  *      A value of "1" indicates that the backend can process requests
151  *      A value of "1" indicates that the backend can process requests
160  *      A value of "1" indicates that the backend can process requests
170  *      A value of "1" indicates that the backend can keep the grants used
172  *      used in all transactions. The maximum number of grants the backend
175  *      feature the backend doesn't need to unmap each grant, preventing
176  *      costly TLB flushes. The backend driver should only map grants
177  *      persistently if the frontend supports it. If a backend driver chooses
181  *      and fall back to non-persistent mode. Backend implementations may
186  *      If a backend driver wants to limit the maximum number of persistently
190  *      backend driver paired with a LIFO queue in the frontend will
212  *------------------------- Backend Device Properties -------------------------
218  *      This optional property, set by the toolstack, instructs the backend
220  *      is missing the backend should offer discard if the backing storage
244  *      A value of "1" indicates that the backend can process BLKIF_OP_DISCARD
268  *      The physical block size, in bytes, of the backend storage. This
274  *      The size of the backend device, expressed in units of "sector-size".
294  *      The Xen grant reference granting permission for the backend to map
303  *      permission for the backend to map the page of the ring located
340  *      for all transactions, allowing the backend to map them with write
344  *      since the the backend driver will still try to map those grants
347  *      persistent mode even when the backend doesn't support it.
351  *      grants gets used commonly. This is done in case the backend driver
361  *      value supplied in the backend info, whatever that may be set to.
396  *     backend should provide both discard-granularity and discard-alignment.
407  *     page to the backend.  When using a multi-page ring, the 'ring-ref'
413  * (8) The frontend driver has to allow the backend driver to map all grants
427  * If supported, the backend will write the key "multi-queue-max-queues" to
432  * greater than zero, and no more than the value reported by the backend in
436  * ring-ref keys are written as before, simplifying the backend processing
485  *  o Query virtual device               o Query backend device identification
487  *  o Setup OS device instance.          o Open and validate backend device.
488  *                                       o Publish backend features and
495  * o Query backend features and
510  *                                       o Publish backend device properties.
516  *  o Query backend device properties.
528  *         waiting for the backend to enter XenbusStateInitWait.  In this
533  *       o A backend may transition to XenbusStateInitialised, bypassing
537  *         published by the backend must contain their default values.
573  * Indicate to the backend device that a region of storage is no longer in
595  * Recognized if "feature-max-indirect-segments" in present in the backend
597  * number of segments allowed by the backend per request. If the node is
600  * maximum number of indirect segments is fixed by the backend, but the
602  * it's less than the number provided by the backend. The indirect_grefs field
613  * If a backend does not recognize BLKIF_OP_INDIRECT, it should *not*