On Fri, Jan 05, 2018 at 06:10:39AM -0800, Tonghao Zhang wrote:
> This patch adds the name for vhost-user reconnect thread.
> It can help us to know whether the thread is running.
>
> Signed-off-by: Tonghao Zhang <xiangxia.m....@gmail.com>
> ---
> lib/librte_vhost/socket.c | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/lib/librte_vhost/socket.c b/lib/librte_vhost/socket.c
> index d44a0f1..c2e34e0 100644
> --- a/lib/librte_vhost/socket.c
> +++ b/lib/librte_vhost/socket.c
> @@ -433,6 +433,7 @@ struct vhost_user_reconnect_list {
> vhost_user_reconnect_init(void)
> {
> int ret;
> + char thread_name[RTE_MAX_THREAD_NAME_LEN];
>
> ret = pthread_mutex_init(&reconn_list.mutex, NULL);
> if (ret < 0) {
> @@ -449,6 +450,13 @@ struct vhost_user_reconnect_list {
> RTE_LOG(ERR, VHOST_CONFIG,
> "failed to destroy reconnect mutex");
> }
> + } else {
> + snprintf(thread_name, RTE_MAX_THREAD_NAME_LEN,
> + "vhost-reconn");
> +
> + if (rte_thread_setname(reconn_tid, thread_name))
> + RTE_LOG(DEBUG, VHOST_CONFIG,
> + "Failed to set thread name for vhost-user reconnect");
Applied to dpdk-next-virtio, with the intendation fixed.
I have also shortten the log a bit "failed to set reconnect thread name".
There is no need to specify "vhost-user" again since VHOST_CONFIG tells
you it comes from vhost-user.
Thanks.
--yliu
