From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.mhcomputing.net (master.mhcomputing.net [74.208.46.186]) by dpdk.org (Postfix) with ESMTP id 60282DE4 for ; Thu, 23 Apr 2015 02:20:48 +0200 (CEST) Received: by mail.mhcomputing.net (Postfix, from userid 1000) id 928B380BD84; Wed, 22 Apr 2015 17:19:14 -0700 (PDT) Date: Wed, 22 Apr 2015 17:19:14 -0700 From: Matthew Hall To: Stephen Hemminger Message-ID: <20150423001914.GB5966@mhcomputing.net> 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> 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 00:20:48 -0000 On Wed, Apr 22, 2015 at 03:57:44PM -0700, Stephen Hemminger wrote: > 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. Why not try to opportunistically make the code easier to debug? DPDK is not always the easiest thing to debug, but at least it's way better than the kernel. Matthew.