Lines Matching full:frontend
86 * granted to the frontend.
171 * by the frontend driver mapped, so the same set of grants should be
177 * persistently if the frontend supports it. If a backend driver chooses
178 * to use the persistent protocol when the frontend doesn't support it,
180 * (due to the fact that the frontend won't be reusing the same grants),
183 * notifying the frontend depending on memory constraints (this might
190 * backend driver paired with a LIFO queue in the frontend will
219 * to offer (or not to offer) discard to the frontend. If the property
261 * set to 512, unless the frontend advertizes a non-zero value
279 * Frontend XenBus Nodes
301 * For a frontend providing a multi-page ring, a "number of ring pages"
319 * The size of the frontend allocated request ring buffer in units
329 * The size of the frontend allocated request ring buffer in units of
339 * A value of "1" indicates that the frontend will reuse the same grants
341 * access (even when it should be read-only). If the frontend hits the
346 * the previous protocol, a frontend driver can choose to work in
349 * It is recommended that the frontend driver stores the persistently
359 * A value of "1" indicates that the frontend will correctly supply and
363 * that the frontend requires that the logical block size is 512 as it
364 * is hardcoded (which is the case in some frontend implementations).
375 * frontend's domain. (e.g. "The first ATA disk", "The third SCSI
397 * Providing just one of the two may be considered an error by the frontend.
413 * (8) The frontend driver has to allow the backend driver to map all grants
417 * grants that can be persistently mapped in the frontend driver, but
437 * to avoid distinguishing between a frontend that doesn't understand the
444 * For example, a frontend with two queues must write the following set of
457 * For example, a frontend requests two queues/rings and the size of each ring
507 * o Query frontend transport parameters.
527 * o A frontend may transition to XenbusStateInitialised without
530 * transport parameters published by the frontend must contain
534 * XenbusStateInitWait, without waiting for the frontend to first
598 * present, the frontend might use blkif_request_indirect structs in order to
601 * frontend can issue requests with any number of indirect segments as long as
603 * in blkif_request_indirect should be filled by the frontend with the
634 * of the "feature-large-sector-size" frontend xenbus node above for