Lines Matching refs:Ring

205 "Available Ring", and answered (processed) requests show up on the "Used Ring".
220 Ring       |DescIdx|DescIdx|DescIdx|DescIdx|DescIdx|
240 Ring    |DescIdx:Len|DescIdx:Len|DescIdx:Len|DescIdx:Len|DescIdx:Len|
267 Finally, the guest populates the Available Ring with the indices of the head
268 descriptors. All descriptor indices on both the Available Ring and the Used
269 Ring are even.
273 - The host consumes a descriptor index off the Available Ring. This index is
281 - The host places the index of the head descriptor, 2*N, onto the Used Ring,
282   and sets the Len field in the same Used Ring Element to the total number of
286 - VirtioNetReceive polls the Used Ring. If a new Used Ring Element shows up, it
288   descriptor (ie. 2*N) to the Available Ring.
291   the order of head descriptor indices on each of the Available Ring and the
292   Used Ring is virtually random. (Except right after the initial population in
293   VirtioNetInitRx, when the Available Ring is full and increasing, and the Used
294   Ring is empty.)
296 - If the Available Ring is empty, the host is forced to drop packets. If the
297   Used Ring is empty, VirtioNetReceive returns EFI_NOT_READY (no packet
315   Available Ring. The caller is responsible to hang on to the unmodified buffer
331   descriptor's index is pushed on the Available Ring.
333 - The host moves the head descriptor index from the Available Ring to the Used
334   Ring when it transmits the packet.
336 - Client code calls VirtioNetGetStatus. In case the Used Ring is empty, the
338   consumed from the Used Ring and recycled to the private stack. The client
343 - The Len field of the Used Ring Element is not checked. The host is assumed to
352   from the Available Ring to the Used Ring (out of order transmission). Because
354   tracking) the order of head descriptor indices on either Ring is