From: Ravi Kerur <rkerur@gmail.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] Use pthread_setname APIs
Date: Mon, 27 Jul 2015 13:40:08 -0700 [thread overview]
Message-ID: <CAFb4SLC0waLvTB4ad85yKGkFFXvsQ_NqFMjE3akHH6nsxnmqwA@mail.gmail.com> (raw)
In-Reply-To: <2280623.OZV87NhkWH@xps13>
On Sun, Jul 26, 2015 at 2:54 PM, Thomas Monjalon <thomas.monjalon@6wind.com>
wrote:
> Hi Ravi,
> It seems to be a nice improvement but it needs some cleanup.
>
> Checkpatch returns some errors.
>
> 2015-04-22 14:06, Ravi Kerur:
> > use pthread_setname_np and pthread_set_name_np for Linux and
> > FreeBSD respectively.
> > Restrict pthread name len to 16 via config for both Linux and FreeBSD.
>
> One of the most important part of the commit message is to answer why.
> Here you probably should explain that the goal is to help debugging.
>
Sure will do it and will run checkpatch before next version.
>
> > #
> > +# Max pthread name len
> > +#
> > +CONFIG_RTE_MAX_THREAD_NAME_LEN=16
>
> It doesn't have to be configurable. A define would be sufficient.
>
Had run into issues(reported by Bruce) as name_len = 32 worked fine for
FreeBSD but not for Linux, hence thought of making it configurable for
Linux/FreeBSD and be able to have different name len's. Found out that
there is also a definition PTHREAD_MAX_NAMELEN_NP, if it's available on
both Linux and FreeBSD I will use this, else should I restrict name_len =
16?
>
> > + snprintf(thread_name, RTE_MAX_THREAD_NAME_LEN,
> "print-stats");
>
> Why not put this line just before use of thread_name?
>
Will do it.
>
> > +
> > + ret = pthread_create(&tid, NULL, (void*)print_stats, NULL
> );
> > +
> > + if (ret != 0)
> > + rte_exit(EXIT_FAILURE,
> > + "Cannot create print-stats thread\n");
> > +
> > + ret = pthread_setname_np(tid, thread_name);
> > +
> > + if (ret != 0)
> > + RTE_LOG(ERR, VHOST_CONFIG,
> > + "Cannot set print-stats name\n");
> [...]
>
> > + pthread_set_name_np(lcore_config[i].thread_id,
> > + (const char *)thread_name);
>
> Is const casting really needed?
>
Function signature has a (const char *) for second parameter, I will double
check and remove if not needed.
next prev parent reply other threads:[~2015-07-27 20:40 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 [this message]
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
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=CAFb4SLC0waLvTB4ad85yKGkFFXvsQ_NqFMjE3akHH6nsxnmqwA@mail.gmail.com \
--to=rkerur@gmail.com \
--cc=dev@dpdk.org \
--cc=thomas.monjalon@6wind.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).