Vhost-cuse was invented before vhost-user exist. The both are actually doing the same thing: a vhost-net implementation in user space. But they are not exactly the same thing.
Firstly, vhost-cuse is harder for use; no one seems to care it, either. Furthermore, since v2.1, a large majority of development effort has gone to vhost-user. For example, we extended the vhost-user spec to add the multiple queue support. We also added the vhost-user live migration at v16.04 and the latest one, vhost-user reconnect that allows vhost app restart without restarting the guest. Both of them are very important features for product usage and none of them works for vhost-cuse. You now see that the difference between vhost-user and vhost-cuse is big (and will be bigger and bigger as time moves forward), that you should never use vhost-cuse, that we should drop it completely. The remove would also result to a much cleaner code base, allowing us to do all kinds of extending easier. So here to mark vhost-cuse as deprecated in this release and will be removed in the next release (v16.11). Signed-off-by: Yuanhan Liu <yuanhan.liu at linux.intel.com> --- doc/guides/rel_notes/deprecation.rst | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst index f502f86..ee99558 100644 --- a/doc/guides/rel_notes/deprecation.rst +++ b/doc/guides/rel_notes/deprecation.rst @@ -41,3 +41,7 @@ Deprecation Notices * The mempool functions for single/multi producer/consumer are deprecated and will be removed in 16.11. It is replaced by rte_mempool_generic_get/put functions. + +* The vhost-cuse will be removed in 16.11. Since v2.1, a large majority of + development effort has gone to vhost-user, such as multiple-queue, live + migration, reconnect etc. Therefore, vhost-user should be used instead. -- 1.9.0