On Monday 19 May 2008 00:27:05 Avi Kivity wrote:
> Rusty Russell wrote:
> > OK. And since the current situation is that the host doesn't throttle,
> > the feature bit should be "don't throttle, host is doing it for you", and
> > Mark's patch should go in...
>
> Yes.
>
> We should have thought of this before, though, especially as Xen does
>
> this or something very similar:
> > /* Shared ring page */ \
> > struct __name##_sring { \
> > RING_IDX req_prod, req_event; \
> > RING_IDX rsp_prod, rsp_event; \
> > uint8_t pad[48]; \
> > union __name##_sring_entry ring[1]; /* variable-length */ \
> > }; \
>
> req_event and rsp_event allow the other side to indicate when it wants a
> notification.
Well, we do have such a thing, in the ring suppression flags. Note that DaveM
is talking about moving network tx queue into the net drivers themselves,
which will make them much more efficient (ie. drain entire queue before
kick), which may again change the balance of what the Right Thing is.
I'll merge Mark's patch, and look at hacking up a feature to change behaviour
to never suppress tx-done interrupts.
Thanks,
Rusty.
_______________________________________________
Virtualization mailing list
Virtualization@xxxxxxxxxxxxxxxxxxxxxxxxxx
https://lists.linux-foundation.org/mailman/listinfo/virtualization
