[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] [PATCH v4 1/5] public/io/netif.h: document the reality of netif_rx_request/reponse id
>>> On 19.10.15 at 15:53, <paul.durrant@xxxxxxxxxx> wrote: > The id field of the netif_rx_request_t abd netif_rx_response_t structures > is actually useless. > > Because GSO metadata is passed from backend to frontend using > netif_extra_info segments, which do not carry information stating which > netif_rx_request_t was consumed to free up their slot, frontends assume > that the consumed request is the one that previously occupied that same > slot in the shared ring. Also, whilst theoretically possible for other > responses to be re-ordered, they never have been and that assumption has > always been baked into Linux xen-netfront. Is all this true even for frontends not supporting GSO and other "extra" stuff? Jan _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |