Michael S. Tsirkin wrote: >> That saves us the new API (at the expense of a lot more code, but with >> added flexibility). >> > > So we'll probably need to rename request_vqs to request_vectors, > but we probably still need the driver to pass the number of > vectors it wants to the transport. Right? > > I don't think so - virtio will provide the number of interrupts it supports, and virtio-net will tell it to bind ring X to interrupt Y. -- I have a truly marvellous patch that fixes the bug which this signature is too narrow to contain. _______________________________________________ Virtualization mailing list Virtualization@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/virtualization
