From: Matthew Hall <mhall@mhcomputing.net>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] Use pthread_setname APIs
Date: Wed, 22 Apr 2015 17:19:14 -0700 [thread overview]
Message-ID: <20150423001914.GB5966@mhcomputing.net> (raw)
In-Reply-To: <20150422155744.6c41b35d@urahara>
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.
next prev parent reply other threads:[~2015-04-23 0:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-22 21:05 Ravi Kerur
2015-04-22 21:06 ` Ravi Kerur
2015-07-26 21:54 ` Thomas Monjalon
2015-07-27 20:40 ` Ravi Kerur
2015-07-27 21:09 ` Stephen Hemminger
2015-07-27 21:48 ` Ravi Kerur
2015-04-22 22:57 ` Stephen Hemminger
2015-04-23 0:19 ` Matthew Hall [this message]
2015-04-23 0:39 ` Stephen Hemminger
2015-04-23 0:52 ` Matthew Hall
2015-04-23 8:16 ` Bruce Richardson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150423001914.GB5966@mhcomputing.net \
--to=mhall@mhcomputing.net \
--cc=dev@dpdk.org \
--cc=stephen@networkplumber.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).