9ebcd4f9c7
DPDK vhost-user just acts as server so far, so, using a struct named as "vhost_server" is okay. However, if we add client mode, it doesn't make sense any more. Here renames it to "vhost_user_socket". There was no obvious wrong about "connfd_ctx", but I think it's obviously better to rename it to "vhost_user_connection", as it does represent a connection, a connection between the backend (DPDK) and the frontend (QEMU). Similarly, few more renames are taken, such as "vserver_new_vq_conn" to "vhost_user_new_connection". Signed-off-by: Yuanhan Liu <yuanhan.liu@linux.intel.com> |
||
|---|---|---|
| app | ||
| config | ||
| doc | ||
| drivers | ||
| examples | ||
| lib | ||
| mk | ||
| pkg | ||
| scripts | ||
| tools | ||
| .gitignore | ||
| GNUmakefile | ||
| LICENSE.GPL | ||
| LICENSE.LGPL | ||
| MAINTAINERS | ||
| Makefile | ||
| README | ||
DPDK is a set of libraries and drivers for fast packet processing. It supports many processor architectures and both FreeBSD and Linux. The DPDK uses the Open Source BSD license for the core libraries and drivers. The kernel components are GPLv2 licensed. Please check the doc directory for release notes, API documentation, and sample application information. For questions and usage discussions, subscribe to: users@dpdk.org Report bugs and issues to the development mailing list: dev@dpdk.org