On 10/3/24 10:11, Maxime Coquelin wrote:
In order to avoid breaking Vhost-user live-migration, we want the
rte_vhost_driver_set_max_queue_num API to only be effective with
VDUSE.
Furthermore, this API is only really needed for VDUSE where the
device number of queues is defined by the backend.
On Thu, Oct 3, 2024 at 10:11 AM Maxime Coquelin
wrote:
>
> In order to avoid breaking Vhost-user live-migration, we want the
> rte_vhost_driver_set_max_queue_num API to only be effective with
> VDUSE.
>
> Furthermore, this API is only really needed for VDUSE where the
> device number of queues is
In order to avoid breaking Vhost-user live-migration, we want the
rte_vhost_driver_set_max_queue_num API to only be effective with
VDUSE.
Furthermore, this API is only really needed for VDUSE where the
device number of queues is defined by the backend. For Vhost-user,
this is defined by the fronte
3 matches
Mail list logo