Lines Matching refs:backend
47 traditional PV frontend and backend format. The PV frontend is used by
48 the client to send commands to the server. The PV backend is used by the
52 supported by the backend. The size of every ring is also configurable
53 and can span multiple pages, up to the maximum supported by the backend
64 The frontend and the backend connect via xenstore to exchange
68 Multiple rings are supported for each frontend and backend connection.
72 Backend specific properties, written by the backend, read by the
78 List of comma separated protocol versions supported by the backend.
96 backend:
121 Protocol version, chosen among the ones supported by the backend
139 The Xen grant reference granting permission for the backend to
149 - Query virtual device - Query backend device
151 - Setup OS device instance. - Publish backend features
170 - Query backend device properties.
178 Once frontend and backend are connected, they have a shared page per
239 **max-ring-page-order**, as specified by the backend on XenBus.
247 consumer is the backend.
249 It contains server responses. The producer is the backend, the
254 data has already been consumed by the backend. **out_prod** is
256 is increased by the backend, after reading data from **out**.
260 array. **in_prod** is increased by the backend, after writing data to
297 in -> backend to frontend only
298 out-> frontend to backend only
301 backend is the producer. Everything is the same but mirrored for the
304 The producer, the backend in this case, never reads from the **in**
369 The producer (the backend for **in**, the frontend for **out**) writes to the
381 The consumer (the backend for **out**, the frontend for **in**) reads from the