Lines Matching full:as
18 * implicit dependency on the MAX_SKB_FRAGS as the maximum number of
19 * ring slots a skb can use. Netfront / netback may not work as
39 * that it cannot safely queue packets (as it may not be kicked to send them).
45 * advertises it via xenstore as 0 (disabled) or 1 (enabled).
48 * channels for TX and RX, advertise them to backend as
51 * node as before.
72 * ring-ref keys are written as before, simplifying the backend processing
96 * choose not to connect any queues, instead treating the request as an
139 * containing XEN_NETIF_EXTRA_TYPE_MCAST_{ADD,DEL} extra-info fragments as
156 * Some features, such as hashing (detailed below), require a
172 * as a mailbox interrupt. These keys must be set before the frontend
177 * the same as a transmit or receive ring.
179 * order as requests.
191 * interpreted by the frontend as the link being down (no carrier) and a
192 * value of "1" should be interpreted as the link being up (carrier
219 * A hash calculated over an IP version 4 header as follows:
231 * A hash calculated over an IP version 4 header and TCP header as
246 * A hash calculated over an IP version 6 header as follows:
258 * A hash calculated over an IP version 6 header and TCP header as
286 * This algorithm uses a 'key' as well as the data buffer itself.
287 * (Buffer[] and Key[] are treated as shift-registers where the MSB of
621 * the packet header, use it as an index into the table (modulo the size
868 * netfront does not make use of the rx response id (because, as
871 * slot as their corresponding request. Thus, to maintain
886 * assume that it is in the same ring slot as the request that was
923 * features required to process this packet, such as ECN