From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by dpdk.org (Postfix) with ESMTP id 8A3F458F3 for ; Thu, 23 Apr 2015 10:16:36 +0200 (CEST) Received: from orsmga003.jf.intel.com ([10.7.209.27]) by orsmga102.jf.intel.com with ESMTP; 23 Apr 2015 01:16:36 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.11,629,1422950400"; d="scan'208";a="560537297" Received: from unknown ([10.237.220.106]) by orsmga003.jf.intel.com with SMTP; 23 Apr 2015 01:16:33 -0700 Received: by (sSMTP sendmail emulation); Thu, 23 Apr 2015 09:16:31 +0025 Date: Thu, 23 Apr 2015 09:16:31 +0100 From: Bruce Richardson To: Stephen Hemminger Message-ID: <20150423081631.GB8592@bricha3-MOBL3> References: <1429736748-16874-1-git-send-email-rkerur@gmail.com> <20150422155744.6c41b35d@urahara> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150422155744.6c41b35d@urahara> Organization: Intel Shannon Ltd. User-Agent: Mutt/1.5.23 (2014-03-12) Cc: dev@dpdk.org Subject: Re: [dpdk-dev] [PATCH] Use pthread_setname APIs X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Apr 2015 08:16:37 -0000 On Wed, Apr 22, 2015 at 03:57:44PM -0700, Stephen Hemminger wrote: > On Wed, 22 Apr 2015 14:05:48 -0700 > Ravi Kerur wrote: > > > Add code to set names to threads via pthread APIs. > > In Linux corresponding _getname_ is available, however, FreeBSD > > doesn't have corresponding _get_name API available yet. Hence _getname_ > > is not yet used in the code. > > > > Ravi Kerur (1): > > Use pthread_setname apis > > > > config/common_bsdapp | 5 +++++ > > config/common_linuxapp | 5 +++++ > > examples/vhost/Makefile | 1 + > > examples/vhost/main.c | 18 ++++++++++++++++-- > > examples/vhost_xen/Makefile | 1 + > > examples/vhost_xen/main.c | 20 ++++++++++++++++++-- > > lib/librte_eal/bsdapp/eal/eal.c | 7 +++++++ > > lib/librte_eal/linuxapp/eal/Makefile | 2 ++ > > lib/librte_eal/linuxapp/eal/eal.c | 11 +++++++++++ > > lib/librte_eal/linuxapp/eal/eal_interrupts.c | 20 +++++++++++++++++--- > > lib/librte_eal/linuxapp/eal/eal_pci_vfio_mp_sync.c | 16 ++++++++++++++-- > > lib/librte_eal/linuxapp/eal/eal_timer.c | 11 ++++++++++- > > 12 files changed, 107 insertions(+), 10 deletions(-) > > > > Since it possible to have multiple DPDK applications in same environment, > and the thread name size is so limited, I wonder if this is a good idea. Can you be a bit more specific as to what your concern here is? This looks a good idea to me. /Bruce