From: Stephen Hemminger <stephen@networkplumber.org>
To: Ravi Kerur <rkerur@gmail.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] Use pthread_setname APIs
Date: Wed, 22 Apr 2015 15:57:44 -0700 [thread overview]
Message-ID: <20150422155744.6c41b35d@urahara> (raw)
In-Reply-To: <1429736748-16874-1-git-send-email-rkerur@gmail.com>
On Wed, 22 Apr 2015 14:05:48 -0700
Ravi Kerur <rkerur@gmail.com> 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.
next prev parent reply other threads:[~2015-04-22 22:57 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 [this message]
2015-04-23 0:19 ` Matthew Hall
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=20150422155744.6c41b35d@urahara \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=rkerur@gmail.com \
/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).