Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 08 Sep 2014 16:17:46 -0700
From:      Peter Grehan <grehan@freebsd.org>
To:        Nikolay Denev <ndenev@gmail.com>
Cc:        freebsd-virtualization@freebsd.org
Subject:   Re: Bhyve virtio-net indirect descriptors
Message-ID:  <540E391A.6040701@freebsd.org>
In-Reply-To: <CA%2BP_MZHe1K7LE6ruVUc7A1Z4oeLKAHJfChSWt_6x=om7F3=Z=g@mail.gmail.com>
References:  <CA%2BP_MZHe1K7LE6ruVUc7A1Z4oeLKAHJfChSWt_6x=om7F3=Z=g@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Hi Nikolay,

> 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 
for receive.

  Did you have any particular guests in mind ?

later,

Peter.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?540E391A.6040701>