From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ig0-f182.google.com (mail-ig0-f182.google.com [209.85.213.182]) by dpdk.org (Postfix) with ESMTP id AC0836942 for ; Thu, 23 Apr 2015 02:39:40 +0200 (CEST) Received: by igbpi8 with SMTP id pi8so1271822igb.0 for ; Wed, 22 Apr 2015 17:39:40 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=kiuR6l8BUlyWN5pyp05/VxksBjPW7mV6W8v5QDlcyds=; b=gtLzNGL8cEESLW3/1hUwKMGjuUgJxZgboiznCovp2J+kdMrsi080CipSVxRKp5lQba 4ltJQFZrirkOyohiBB83sOWt1Zm2dnNACIwZ7ejoWwuvDtJRBaJbTk0liHpG+bfd4WUB om2g+L8go878/jExj8srwq/TSIBWprk3OyK1g9XoPtsyYKPzf/rvxVne0PQXPhojPAHh RO6jGLn/y0WqQoV2E9U1neqEbLEsMHcamktdXRlE/PlkRFUF9yebQx6XeSZesVjtos5t 2f8ffjqA39Uaksh0XHf/c/qrQRJ2exD1t5C2B5VePCMdr4rr0PF6pFGK5cfe4HyQS2Gz P0CQ== X-Gm-Message-State: ALoCoQl5C48UHk8FEZpAVIW8+jorHvZ/HRuWXdqqdh70Q99ykiW27nFEbhC18tWDQ8XZAjwLK1Ud MIME-Version: 1.0 X-Received: by 10.50.64.243 with SMTP id r19mr924764igs.5.1429749580142; Wed, 22 Apr 2015 17:39:40 -0700 (PDT) Received: by 10.64.58.227 with HTTP; Wed, 22 Apr 2015 17:39:40 -0700 (PDT) In-Reply-To: <20150423001914.GB5966@mhcomputing.net> References: <1429736748-16874-1-git-send-email-rkerur@gmail.com> <20150422155744.6c41b35d@urahara> <20150423001914.GB5966@mhcomputing.net> Date: Wed, 22 Apr 2015 17:39:40 -0700 Message-ID: From: Stephen Hemminger To: Matthew Hall Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.15 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:39:41 -0000 In our application we already use setname and have a policy for what the names look like. This won't help On Wed, Apr 22, 2015 at 5:19 PM, Matthew Hall wrote: > 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. >