Home
last modified time | relevance | path

Searched refs:rte_vhost_driver_start (Results 1 – 11 of 11) sorted by relevance

/dpdk/lib/vhost/
H A Dversion.map33 rte_vhost_driver_start;
H A Drte_vhost.h626 int rte_vhost_driver_start(const char *path);
H A Dsocket.c1101 rte_vhost_driver_start(const char *path) in rte_vhost_driver_start() function
H A Dvhost_crypto.c1422 return rte_vhost_driver_start(path); in rte_vhost_crypto_driver_start()
/dpdk/examples/vdpa/
H A Dmain.c195 if (rte_vhost_driver_start(socket_path) < 0) in start_vdpa()
/dpdk/examples/vhost_blk/
H A Dvhost_blk.c899 ret = rte_vhost_driver_start(dev_pathname); in main()
/dpdk/doc/guides/prog_guide/
H A Dvhost_lib.rst183 * ``rte_vhost_driver_start(path)``
/dpdk/examples/vhost/
H A Dmain.c1936 if (rte_vhost_driver_start(file) < 0) { in main()
/dpdk/drivers/net/vhost/
H A Drte_eth_vhost.c1041 if (rte_vhost_driver_start(internal->iface_name) < 0) { in vhost_driver_setup()
/dpdk/doc/guides/rel_notes/
H A Drelease_17_05.rst384 ``rte_vhost_driver_start`` should be used, and there is no need to create
H A Drelease_20_11.rst515 instead of ``rte_vhost_driver_start`` by crypto applications.