Any reason why bhyve is not advertising indirect descriptors for virtio-net?
Indirect descriptors never seemed to make a lot of sense to me for
networking. It requires allocations at the end of the transmit path
which could potentially fail, or requires large amounts of preallocation
to deal with maximum-sized segments. So, the initial version of bhyve's
virtio-net didn't support it since I felt it impacted guest drivers.
However, with Chris Torek's contribution of virtio.c, the additional
work of dealing with the descriptors is hidden in the virtio api. For
transmit it should just work, but there has to be some extra code added
Did you have any particular guests in mind ?
email@example.com mailing list
To unsubscribe, send any mail to