> -----Original Message-----
> From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Tiwei Bie
> Sent: Monday, June 25, 2018 1:02 PM
> <snip>
> 
> Hi Dariusz,
> 

Hi Tiwei,

> Thank you for putting efforts in making the DPDK
> vhost more generic!
> 
> From my understanding, your proposal is that:
> 
> 1) Introduce rte_vhost2 to provide the APIs which
>    allow users to implement vhost backends like
>    SCSI, net, crypto, ..
> 

That's right.

> 2) Refactor the existing rte_vhost to use rte_vhost2.
>    The rte_vhost will still provide below existing
>    sets of APIs:
>     1. The APIs which allow users to implement
>        external vhost backends (these APIs were
>        designed for SPDK previously)
>     2. The APIs provided by the net backend
>     3. The APIs provided by the crypto backend
>    And above APIs in rte_vhost won't be changed.

That's correct. Rte_vhost would register its own rte_vhost2_tgt_ops underneath 
and will call existing vhost_device_ops for e.g. starting the device once all 
queues are started.
Regards,
D.

> 
> Is my above understanding correct? Thanks!
> 
> Best regards,
> Tiwei Bie
> 

Reply via email to