Lines Matching full:backend

34  * Older implementation of Xen network frontend / backend has an
37  * expected when frontend and backend have different MAX_SKB_FRAGS.
42  * slots backend must support.
45  * (18), which is proved to work with most frontends. Any new backend
55  * feature 'feature-rx-notify' via xenbus. Otherwise the backend will assume
61  * and RX notification. Backend either doesn't support this feature or
65  * channels for TX and RX, advertise them to backend as
73  * If supported, the backend will write the key "multi-queue-max-queues" to
78  * must be greater than zero, and no more than the value reported by the backend
89  * ring-ref keys are written as before, simplifying the backend processing
112  * If there is any inconsistency in the XenStore data, the backend may
118  * transmitting system (backend or frontend) and is not negotiated
141  * backend. If the frontend wishes to take advantage of this feature then
142  * it may set "request-multicast-control". If the backend only advertises
144  * before the frontend moves into the connected state. The backend will
146  * value will have no effect. However, if the backend also advertises
148  * may be set by the frontend at any time. In this case, the backend will
152  * backend transmit side should no longer flood multicast packets to the
169  * backend. Use of xenstore is not suitable for large quantities of data
171  * The ability of the backend to use a control ring is advertised by
174  * /local/domain/X/backend/vif/<domid>/<vif>/feature-ctrl-ring = "1"
176  * The frontend provides a control ring to the backend by setting:
197  * The backend can advertise its current link (carrier) state to the
198  * frontend using the /local/domain/X/backend/vif/<domid>/<vif>/carrier
427  * the backend. The message of type XEN_NETIF_CTRL_TYPE_ADD_GREF_MAPPING
429  * The backend will maintain a fixed amount of these mappings.
485  *       hashing and the backend is free to choose how it steers packets
492  * the backend.
513  * This is sent by the frontend to set the types of hash that the backend
539  *       Also, setting data[0] to zero disables hashing and the backend
562  *                                                     than the backend
572  *       The maximum size of key is algorithm and backend specific, but
581  * table supported by the backend. The size is specified in terms of
604  * table to be used by the backend. The size is specified in terms of
631  * hash value to queue number. The backend should calculate the hash from
651  *                                                     than the backend
672  *       The backend may support a mapping table larger than can be
684  * mapped in the backend.
706  * This is sent by the frontend for backend to map a list of grant
729  *       failure none of grants mappings get added in the backend.
734  * This is sent by the frontend for backend to unmap a list of grant
771  * This is the 'wire' format for transmit (frontend -> backend) packets:
790  * (backend -> frontend) packets. Specifically, in a multi-fragment
829  * This is the 'wire' format for receive (backend -> frontend) packets:
848  * (frontend -> backend) packets. Specifically, in a multi-fragment
898  *       consumed to make the slot available, and the backend must ensure
950  * A backend that supports teoplitz hashing is assumed to accept