From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga03.intel.com (mga03.intel.com [134.134.136.65]) by dpdk.org (Postfix) with ESMTP id 4C9215F2D for ; Fri, 23 Mar 2018 02:39:01 +0100 (CET) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by orsmga103.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 22 Mar 2018 18:39:00 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.48,347,1517904000"; d="scan'208";a="30522269" Received: from fmsmsx107.amr.corp.intel.com ([10.18.124.205]) by fmsmga002.fm.intel.com with ESMTP; 22 Mar 2018 18:39:00 -0700 Received: from fmsmsx120.amr.corp.intel.com (10.18.124.208) by fmsmsx107.amr.corp.intel.com (10.18.124.205) with Microsoft SMTP Server (TLS) id 14.3.319.2; Thu, 22 Mar 2018 18:39:00 -0700 Received: from shsmsx101.ccr.corp.intel.com (10.239.4.153) by fmsmsx120.amr.corp.intel.com (10.18.124.208) with Microsoft SMTP Server (TLS) id 14.3.319.2; Thu, 22 Mar 2018 18:38:59 -0700 Received: from shsmsx103.ccr.corp.intel.com ([169.254.4.235]) by SHSMSX101.ccr.corp.intel.com ([169.254.1.166]) with mapi id 14.03.0319.002; Fri, 23 Mar 2018 09:38:58 +0800 From: "Tan, Jianfeng" To: "xiangxia.m.yue@gmail.com" CC: "dev@dpdk.org" Thread-Topic: [PATCH 2/2] vhost: add fdset-event thread name Thread-Index: AQHTwdrt9gpQtCdsP02X4muHtVBn56PdCnkQ Date: Fri, 23 Mar 2018 01:38:58 +0000 Message-ID: References: <1521722398-93353-1-git-send-email-xiangxia.m.yue@gmail.com> <1521722398-93353-2-git-send-email-xiangxia.m.yue@gmail.com> In-Reply-To: <1521722398-93353-2-git-send-email-xiangxia.m.yue@gmail.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.239.127.40] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] [PATCH 2/2] vhost: add fdset-event thread name X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Mar 2018 01:39:02 -0000 > -----Original Message----- > From: xiangxia.m.yue@gmail.com [mailto:xiangxia.m.yue@gmail.com] > Sent: Thursday, March 22, 2018 8:40 PM > To: Tan, Jianfeng > Cc: dev@dpdk.org; Tonghao Zhang > Subject: [PATCH 2/2] vhost: add fdset-event thread name >=20 > From: Tonghao Zhang >=20 > This patch adds the name for vhost fdset thread. > It can help us to know whether the thread is running. >=20 > Signed-off-by: Tonghao Zhang Reviewed-by: Jianfeng Tan Thanks, Jianfeng > --- > lib/librte_vhost/socket.c | 9 +++++++++ > 1 file changed, 9 insertions(+) >=20 > diff --git a/lib/librte_vhost/socket.c b/lib/librte_vhost/socket.c > index 8ca01df..93175ba 100644 > --- a/lib/librte_vhost/socket.c > +++ b/lib/librte_vhost/socket.c > @@ -820,6 +820,7 @@ struct vhost_device_ops const * > { > struct vhost_user_socket *vsocket; > static pthread_t fdset_tid; > + char thread_name[RTE_MAX_THREAD_NAME_LEN]; >=20 > pthread_mutex_lock(&vhost_user.mutex); > vsocket =3D find_vhost_user_socket(path); > @@ -835,6 +836,14 @@ struct vhost_device_ops const * > RTE_LOG(ERR, VHOST_CONFIG, > "failed to create fdset handling thread"); > return ret; > + } else { > + snprintf(thread_name, > RTE_MAX_THREAD_NAME_LEN, > + "vhost-events"); > + > + if (rte_thread_setname(fdset_tid, thread_name)) { > + RTE_LOG(DEBUG, VHOST_CONFIG, > + "failed to set vhost-event thread > name"); > + } > } > } >=20 > -- > 1.8.3.1